Whether your network administrator has configured the two-factor authentication server as accessible from inside the pod's VNet, or is located outside the VNet.

Whether the gateway configuration is internal or external.

Whether you configured a RADIUS or RSA SecurID type on the gateway configuration.

The specific source IPs that the Unified Access Gateway instances use when contacting the two-factor authentication server depend on: Usually your network administrator determines what network access the two-factor authentication server has to the VNet and the subnets that are connected to the deployed pod.

To accept communication from the gateway configuration's Unified Access Gateway instances, two-factor authentication servers need to allow communications from the appropriate IP addresses. This topic describes the information from your Horizon Cloud pod that you must use in your two-factor authentication server to enable communication between the pod's gateway and also to maintain resiliency of that communication after each pod update. As an example, as described in SecurID Authentication Manager Documentation - Add an Authentication Agent, you use the RSA Authentication Manager's Security Console to add the necessary IP addresses to its internal database. etc/raddb/nf file contains the definitions of RADIUS clients as:Īn RSA SecurID two-factor authentication system uses the concept of authentication agents that are registered to communicate with RSA Authentication Manager. As an example, as described in theįreeRADIUS wiki for FreeRADIUS client configuration, the A RADIUS two-factor authentication system uses the concept of allowed RADIUS clients.

Azure radius