This is an Early Access feature. To enable it, please contact Okta Support.
Okta RADIUS support can distinguish between different RADIUS-enabled apps and support them concurrently by setting up an Okta RADIUS app for each configuration. Additionally, the Okta RADIUS application supports policy creation and then assigning RADIUS authentication to groups.
RADIUS-enabled apps are easy to manage, as Admins can manage all of these apps and infrastructure configurations from the Okta Admin Console. It is no longer necessary to make changes on the Okta RADIUS Agent server itself adding security as well as convenience.
Prerequisite: To use the Okta RADIUS application, you must install the Okta RADIUS agent v. 2.5.0 or later. As this is an early-access feature, ask Okta Support for the new agent when you request the feature. To obtain the agent, navigate to Settings > Downloads and select the Download link next to the RADIUS application.
Okta RADIUS App Features
Support for multiple RADIUS enabled apps and infrastructure
Each app and infrastructure component, such as VPNs, can be configured differently through the same Okta RADIUS Agent, because the improved RADIUS agent can listen to multiple distinct ports for separate RADIUS configurations; for example, Cisco AnyConnect uses RADIUS UDP port 1812 and another on-prem app could use RADIUS UDP port 1813.
User and group specific configurations
Because of the new app model, you can limit access to specific users and groups as needed the same way you can restrict access to any app. Admins can restrict access to RADIUS enabled apps and infrastructure to specific groups of users instead of all Okta users
Pass group ownership to RADIUS applications
Okta can now pass a list of all groups a user belongs to a RADIUS-enabled app or infrastructure. This allows admins to support fine-grained authorization with different levels of access and security based off the group membership of users.
Provide multifactor authentication and security based on IP addresses
By resolving the IP address of the client attempting to connect to a RADIUS-enabled app or infrastructure admins can adjust levels of access depending on whether a user is within a certain IP range or network zone. For more information on ranges and zones, see Network.
Centralized, Cloud-Based Configuration
Administrators can manage all of their RADIUS-enabled apps and infrastructure configurations from the Okta Admin Console, without making changes on the Okta RADIUS Agent server itself.
2FA Only (Passwordless Mode)
You can configure a RADIUS-enabled app to only use the second factor in multifactor authentication. This is also known as passwordless mode.
When configuring the app, uncheck the box Okta performs primary authentication. The screenshot shown below shows the default configuration, which is not 2FA only. Additionally, the UDP port must be unique. Be sure to verify the Application username format when enabling 2FA mode.
There are three limitations on the Okta RADIUS application.
There are four required steps and two optional steps to upgrade the agent and add a RADIUS application.
Step 1 – Adding the RADIUS App
Adding the RADIUS app is like adding any other app in Okta.
Configuring the RADIUS App
Once created, you'll land on the page for the app, as shown below.
Step 2 – Configure the RADIUS agent
Install RADIUS agent 2.5.0 or later that you downloaded. Earlier versions of the RADIUS agent do not support the new features. For information on installing the RADIUS agent, see Installing and Configuring the Okta RADIUS Agent.
Important: During the agent installation, you might be prompted to enter a RADIUS Shared Secret and a RADIUS port. These values are no longer used; you can enter anything in these fields. These values are no longer used for orgs that have this feature enabled; however, any information entered from these prompts is used for backwards compatibility when an org does not have the feature enabled.
Step 3 – Configure a RADIUS-enabled application
Configure your specific application to point to the Okta RADIUS Agent server to handle RADIUS authentication requests.
Although this will vary based on your specific application or infrastructure, it typically requires:
For more information, please refer to your vendor’s documentation and locate any content pertaining to RADIUS setup.
Step 4 – Validating the app setup
After configuring an on-prem app, VPN, or Amazon Workspaces, validate the integration using any of the following processes:
Step 5 – Client IP Reporting [optional]
If desired, you can configure Okta to enforce, restrict, or provide different levels of access depending on the IP address or network zone of users accessing your RADIUS-enabled system. The following steps outline this process.
After completing the following procedure to enable client-ip resolution, you can define network zones by location or IP address and use them in sign-on policies to provide access, enforce MFA, or block access. For more information, see IP Zones.
Step 6 – Use Okta group membership information for authorization [optional]
You can configure Okta to provide different levels of authorization and access based on the groups to which users belong for a RADIUS-enabled service. Use the following procedure for each app to configure by group membership.
Steps 3-6 refer to the screen shown below.
After successfully completing this configuration, Okta passes group membership information to your RADIUS enabled app or system. You can now log into your app or infrastructure and configure its action based on these specific groups.