Best practice for secure remote access using the ThinLinc native client

I’m interested in understanding what the recommended production architecture is for external users connecting over the Internet using the native client. I have webaccess with MFA and NGNIX as the reverse proxy working but looking at the native client, mainly because of audio support and the best possible graphics performance.

I’ve read the following blog post

Specifically:

  • Is opening SSH (port 22) to the broker(s) via NAT/port forwarding the recommended approach, or is there a better practice?

  • How do most orgs deploy multiple brokers for native client access? Is Nginx or another load balancer commonly used, or should clients connect directly to the broker HA VIP?

    Cheers

    Harj