Use the same user name and password for RADIUS and Windows authentication - Select this option if the initial RADIUS authentication uses Windows authentication that triggers an out-of-band transmission of a token code that is used as part of a RADIUS challenge.
If you do not select this option, the user names can be different. If you select this option, users must use the same RADIUS user name for Active Directory authentication.
Enforce 2-factor and Windows user name matching - Select this option to force RADIUS user names to match user names in Active Directory.
(Optional) Select the check boxes for the appropriate authentication options.
In the Advanced Authentication section, from the 2-factor authentication drop-down list, select RADIUS.
From the navigation menu, select Settings > Servers > Connection Servers.
View Connection Server is also called VMware Horizon 7 Administrator.
Log in to the View Connection Server admin interface as an administrator.
You have an AuthPoint identity provider (IdP) certificate An AuthPoint IdP certificate is required for SAML authentication.
A token is assigned to a user in AuthPoint.
You can use Horizon Client to log in to Connection Server and invoke published app(s) with a user that exists in the Active Directory domain.
Horizon Connection Server has published one or more apps that exist on the Virtual Machine with Horizon Agent installed.
vCenter Server manages a Virtual Machine that has Horizon Agent installed.
Horizon Connection Server is connected to vCenter Server.
This diagram shows an overview of the configuration required for RADIUS authentication.īefore you begin these procedures, make sure that: VMware Horizon 7 Configuration for RADIUS AuthenticationĪuthPoint communicates with various cloud-based services and service providers with the RADIUS protocol.
AD DS, AD CS and DNS on Windows Server 2016.
The hardware and software used in this guide include: