Using the Okta RADIUS Agent for VMware Horizon

In this blog we are going to discuss adding Multi-Factor Authentication using Okta Verify with VMware Horizon by leveraging the Okta Radius Agent.

For more information on this integration, please see https://www.okta.com/integrations/mfa-for-virtual-desktops/vmware/

We are going to walk through 3 separate deployment options to leverage the Okta Radius Client:

  1. Using Workspace ONE Access (formerly known as VMware Identity Manager)
  2. Using Unified Access Gateway (UAG)
  3. Using Horizon Connection Servers

Let’s start with installing and configuring the Okta Radius Agent.

Installing the Okta Radius Agent

For detailed instructions please see: https://help.okta.com/en/prod/Content/Topics/Directory/Agent_Installing_the_Okta_Radius_Agent.htm

  1. Download the Okta RADIUS Agent from the Okta Admin Portal by going to Settings -> Downloads
  1. Once downloaded, launch the installer.
  2. On the intro screen, click next
  3. Click Next accept the license agreement:
  4. Select the correct installation patch and click Install.
  5. Create a Secret that will be used when configuring the radius clients.
  1. If you require a proxy complete this section otherwise click next
  2. Click Next
  3. Enter your tenant name (Note: Do not enter the full URL) with the appropriate instance
  1. You will be redirected to your Okta tenant to Authenticate
  1. Click Allow Access
  1. You can then complete the installation.

Configure the Okta Radius Agent

The configuration for the Okta Radius Agent will be done within the Okta Admin Portal

  1. Click on Applications -> Applications
  2. Click New Application
  3. Search for “VMware Horizon View (RADIUS)” and Click Add
  1. Click Next
  2. Enter the UDP Port (1812)
  3. Enter the radius secret you used previously
  4. Select the correct username to match your environment.
    This is a very important step. For an optimal user experience, this should match your horizon credentials. If you have multiple AD domains in your horizon environment this should include the domain (ie. UPN or EMAIL).

  1. Click Done
  2. Click on the VMware Horizon View (RADIUS) application.
  3. Click Edit for the Advanced Radius Settings
  4. If you want to enable PUSH Notification, make sure the top two boxes are checked

Using Workspace ONE Access (formerly known as VMware Identity Manager)

  1. In the Workspace ONE Access Admin Console, go to Identity & Access Management -> Setup -> Connectors
  2. Click on your Worker to edit your connector configuration
  3. Click on Auth Adapters
  4. Click on the Radius Auth Adapter
  1. This will launch a configuration page running on your connector server.
    You will need connectivity to your connector server to complete this step.
    If you are presented an access denied page you might need to temporary change your policy to Password.
  2. Add your Radius Server Host name, Port and Shared Secret. (Leave the Authentication Type as PAP)
  1. Click Save
  2. Return to the WS1 Access Admin Console and verify the Radius Auth Method is enabled. (You might need to refresh)
  3. Go to Identity & Access Management
  4. Click on Identity Providers
  5. Click on your Built-In Identity Provider
  6. Under Connector Authentication Methods, select Radius (Cloud Deployment)
  1. Click Save
  2. Click on Policies
  3. Edit your appropriate policy to include “Radius (cloud deployment)”. In my example, I’m modifying the Win10 rule in the Default Policy.
  1. Click Save, Next and Save.
  2. Open an Incognito Window and we’ll test the configuration
    Note: If you ever lock yourself out, you can always go to: https://%5BTENANT%5D.vmwareidentity.com/SAAS/auth/0 to login using your System Domain Account.
  3. You will be prompted to enter your Okta Credentials
  1. You should be prompted to approve the authentication on your Okta Verify Application

Using Unified Access Gateway (UAG)

In environments where a Unified Access Gateway is deployed, most customers will typically want to configure MFA here as this appliance typically sits on the network edge. We can configure UAG to prompt for MFA using Okta Verify and then pass the credentials to Horizon to complete the authentication into the view client.

Note: If you have multiple AD domains, you will need to ensure your login through Okta contains the domain name (ie. UPN/Email).

  1. Log into your UAG Admin Console
  2. Under Authentication Settings, click the gear icon for RADIUS
  3. Enable RADIUS, Select PAP and enter the host name and port for the Okta Radius Agent.
  1. Click Save
  2. Expand Edge Service Settings and edit the Horizon Settings
  3. Click on “More” (at the bottom)
  4. Under Auth Methods, select radius-auth
  5. You will also need to enable “Enable Windows SSO” to prevent a subsequent login into the horizon client.
  1. Click Save
  2. Test your configuration by logging into the Horizon Portal. You will be prompted for your Okta username and password
  1. You will then be prompted to approve the Okta Verify request on your device.

Using Horizon Connection Servers

Radius can be configured directly on the Horizon Connection Servers. This allows for MFA to be configured for both internal and external users (assuming internal users are not going through UAG).

Note: If you have multiple AD domains, you will need to ensure your login through Okta contains the domain name (ie. UPN/Email).

  1. Log into your Horizon Admin console
  2. Edit your Connection Server Settings
  3. Under Advanced Authentication, select Radius
  4. Select “Use the same username and password for RADIUS and Windows Authentication
  5. On the Authenticator drop down, select Create New Authenticator
  6. Enter your host name, port and secret for the Okta Radius Agent
  1. Click OK
  1. Click OK.
  2. Test your configuration by logging into the Horizon Portal. You will be prompted for your Okta username and password
  1. You will then be prompted to approve the Okta Verify request on your device.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s