See Enable Two-Factor Authentication on a Horizon Cloud Pod's Gateways and Best Practices When Implementing Two-Factor Authentication in a Universal Broker Environment. If you want Universal Broker to use two-factor authentication for your Horizon Cloud pods, configure the same type of authentication service on each external Unified Access Gateway instance that's on every participating pod.Configure the required ports and protocols, as described in the "Ports and Protocols Required by Universal Broker" section in Horizon Cloud Pods - Ports and Protocols Requirements.See the "Pod Deployment and Operations DNS Requirements" table in DNS Requirements for a Horizon Cloud Pod in Microsoft Azure. Verify that the required DNS names for your regional Universal Broker instance are resolvable and reachable.Select Universal Broker as your tenant-wide connection broker for Horizon pods, as described in Start the Universal Broker Setup.
If you want to enable two-factor authentication only for your external users and bypass it for your internal users, Define Internal Network Ranges for Universal Broker. For more information, see Best Practices When Implementing Two-Factor Authentication in a Universal Broker Environment. If you want Universal Broker to use two-factor authentication for your Horizon pods, configure the appropriate two-factor authentication service on each Unified Access Gateway instance within every participating pod. Horizon Pods - Configure Unified Access Gateway for Use with Universal Broker. #Universal type client change password install#
Horizon Pods - Install the Universal Broker Plugin on the Connection Server.
Configure the required ports, as described in Horizon Pods - DNS, Ports, and Protocol Requirements for Universal Broker. Verifying these prerequisites is especially important when you are completing the wizard for the tenant's first-time setup of Universal Broker. Prepare the required system components according to your pod type. Unified Access Gateway configuration is required for that. Unified Access Gateway, and so the external Universal Broker matches the two-factor authentication settings with the external In the case of two-factor authentication, Unified Access Gateway is required to successfully launch the virtual desktop or remote app from the end-user client after the client has authenticated with In the case of external end users, the external Unified Access Gateway instances that are on the pods. Important: If you will have any end users connecting from the Internet or if you want to use two-factor authentication, do not delete the external For example, if you have a blended pod fleet consisting of both Horizon pods and Horizon Cloud pods and you want to use RADIUS authentication, you configure the RADIUS service on each external Unified Access Gateway instance across all of those Horizon pods and Horizon Cloud pods. The configurations of external Unified Access Gateway instances must be identical within and across participating pods. To use two-factor authentication for Universal Broker, you must first configure the appropriate authentication service on each external Unified Access Gateway instance within every participating pod in your pod fleet. By its default design, the same Universal Broker two-factor authentication settings will be applied tenant-wide, used for each and every pod in the tenant's pod fleet. The Unified Access Gateway then relays the authentication service's response back to the Universal Broker. By design, when Universal Broker is configured with two-factor authentication settings, it forms the authentication request and passes it to an external Unified Access Gateway instance which then communicates with the actual authentication server configured in that instance's settings. Some key points about the two-factor authentication settings in this configuration wizard Then when you find you need to revise the settings during your ongoing use of the service, you can re-open the configuration wizard from the console's Broker page or the Getting Started page. In the first-time setup of Universal Broker, the configuration wizard opens automatically, as described in Start the Universal Broker Setup. Before you can use Universal Broker for the brokering of resources from end-user assignments, you must first configure certain settings.
0 kommentar(er)
