Okta Agent - RADIUS Configuration - Authentication Manager - RSA Ready Implementation Guide
Originally Published: 2021-11-02
This article describes how to add RSA as an authenticator for Okta Agent with RSA Authentication Manager using RADIUS.
Configure RSA Authentication Manager
Perform these steps to configure RSA Authentication Manager using RADIUS.
Procedure
- Sign in to the Security Console.
- Navigate to RADIUS > RADIUS Clients, click Add new, and provide the following details:
- Client Name: Give any suitable name.
- ANY client: Select the checkbox.
- IP address Type: IPV4
- IPv4 Address: IP address of the machine where the Okta agent is installed.
- Make/Model: Standard Radius
- Shared Secret: This should be the same as what was configured in the Okta configuration.
- Click Save & Create Associated RSA Agent.
Note
To mitigate the Blast RADIUS vulnerability, ensure that the Message-Authenticator attribute flag is enabled. Perform the following steps:
- Log in to the Operating console as an administrator.
- Navigate to Deployment Configurations > RADIUS Servers.
- Select the Manage Server Files option.
- Click the drop-down icon against the dynamic-clients file and click Edit.
- To enforce the use of Message-Authenticator attribute across all IPv4 and IPv6 clients, update all four entries of the Message-Authenticator attribute flag (&FreeRADIUS-Client-Require-MA) as follows: "&FreeRADIUS-Client-Require-MA = yes"
- Click Save& Restart RADIUS Server.
For more details on the RADIUS configuration file, refer to the RADIUS Reference Guide.
Configure Okta
Perform the steps in this section to configure RSA as an authenticator in Okta.
Procedure
- Log in to Okta admin console.
- Click Security > Authenticators.
- Click Add Authenticator and select RSA.
- Download the Okta agent and install it on the machine. Ensure the machine where the agent is installed meets the hardware requirements. Note down the Instance ID to be used in the installation.
- Post successful installation, add the following details in the same form:
- Username format: Okta username prefix
- Hostname: IP address of the Authentication manager.
- Authentication Port:1812
- Shared Secret: This should be the same as what is given in the RSA configuration.
- Click Save.
- Navigate to Security > Authentication Policies.
- Make sure the policy for the Okta Admin Console app has RSA SecurID as an Additional factor type.
Notes
- Ensure that the user used for testing the integration is created in Okta also. Navigate to Directory > People to create the user.
- Ensure the application for Okta Admin Console is present and the admin user is assigned to the application.
- Ensure the policy assigned to the application has RSA SecurID as the Additional factor type.
- While testing the integration, provide the complete e-mail address of the user.
The configuration is complete.
Return to Okta Agent - RSA Ready Implementation Guide.
Related Articles
Okta Agent - RADIUS Configuration - Cloud Authentication Service - RSA Ready Implementation Guide 179Number of Views Microsoft NPS - RADIUS Configuration with Authentication Manager - RSA Ready Implementation Guide 16Number of Views Workflow Variables under the Resource section of Workflow Nodes cannot resolve Roles and Groups after being imported in RS… 36Number of Views HPE Aruba ClearPass - RADIUS Configuration with Authentication Manager - RSA Ready Implementation Guide 14Number of Views Check Point Gateway Identity Awareness- SAML Relying Party Configuration for Cloud Authentication Service - RSA Ready Impl… 27Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?