This does not apply to all VPN technologies, as those that can also operate with DTLS or IPsec instead of SSL/TLS can work well with Horizon 7 desktop protocols. With modern video remoting protocols exploiting connectionless UDP-based transports, the performance benefits can be significantly eroded when forced over a TCP-based transport. This implementation meets security requirements and, with Transport Layer Security (TLS) enabled, is considered secure, but the underlying protocol with SSL/TLS is just TCP-based. With Unified Access Gateway, PCoIP, HTML access, and WebSocket protocols are secured without requiring additional encapsulation. Unified Access Gateway is designed to maximize security and performance. A VPN requires that you must set up the VPN software first and authenticate separately before starting the Horizon Client. With Unified Access Gateway, when the Horizon Client is launched, authenticated users are in their View environment and have controlled access to their desktops and applications. Unified Access Gateway does not alter the straightforward Horizon Client user interface. At first, this works well with a VPN, but requires significant administrative effort to maintain the required rules. A VPN does the same, because most VPNs allow an administrator to configure network connection rules for every user or group of users individually.

Gateway configurations on your pod use Unified Access Gateway VMs and are configured to provide your end users' access to their desktops and applications. Unified Access Gateway recognizes the entitlements of the users and the addressing required to connect internally. To enable use of two-factor authentication in the gateway settings of an already deployed pod, use the Edit action in the pod's details page.

Unified Access Gateway applies access rules automatically.

Vmware uag azure mfa