NATS 2.10 Webinar 

12:00 a small correction: TLS handshake was always performed after INFO (that says to a client that TLS is required) and before CONNECT (that carries e.g. client's password). It was never the case that a password would be sent as clear text. The new feature TLS-first is needed in cases when a client connects to e.g. a cloud that accepts *only* TLS. The workaround until now was to use WSS.

and many thanks for the auth callout, I'm really looking forward to NATS-LDAP integration out of the box

Thanks for this great presentation Byron :)

impressive improvements. I 2nd the GUI , as it will make management easier

I still think there should be a gui dashboard that should ship with the binary to allow full control of nats without having to learn and dive into config after config. It's holding nats back imo.

Timestamps 00:24 Highlights 01:18 Stream compression 04:25 Stream storage format 07:50 MQTT QoS 2 08:01 Native MQTT client support 10:20 IBG z/OS and NetBSD 11:57 TLS-first leafnodes 14:50 Auth callout 17:36 v2 networking 27:15 Multi-filter consumers 30:15 Stream subject transforms 34:56 Demo (Auth callout + OAuth2) 53:00 Q&A

Lovely session, thank you so so much! Learning a lot. Love demos like this. Just to "throw it out there": maybe auth callout could be combined nicely with Open Policy Agent?!? 🤔 (Don't need it myself right now, but the idea might be inspiring for someone..).

Are different TCP Destination Ports needed for the multi TCP Connections or are they just identified by Source Port where the Client opens multiple TCP Connections to the same Server Port, meaning Firewalls or k8s Services are unaware about the multiple TCP connections?

AFAIK MQTT5 support REQ/REPLY Semantics, does it makes sense ot have this in the MQTT Bridge ?

Where is the auth0 integration code repo?