Install and configure the RADIUS agent in AWS
During this task we will configure the install and configure the RADIUS agent into an AWS instance.
Before you begin
- Ensure that you have the common UDP port and secret key values available.
Port 1899 is used throughout this integration.
Install the RADIUS Agent
The following steps should be completed on the AWS instance described as Instance B.
When installing the RADIUS Agent, you must be logged in to an account that either has both Read-only Admin, and App admin roles, or has the Super admin role.
In addition, Okta recommends the use of dedicated service account to authorize RADIUS agents. A dedicated account ensures that the API token used by the RADIUS agent is not tied to the life-cycle of a specific user account which could be deactivated when the user is deactivated. In addition, service accounts used for RADIUS agents must be given appropriate admin permissions.
From your Administrator Dashboard, select.
Scroll to Okta RADIUS Server Agent (EXE) and click Download Latest.
Run the installer. Click Next on each of the initial, Important Information, and License Information screens.
Choose a location for the Installation folder and click Install.
On the Okta RADIUS Agent Proxy Configuration screen, you can optionally enter your proxy information. Click Next.
On the Register Okta RADIUS Agent screen, enter the complete URL for your org (for example, https://mycompany.okta.com). For testing in your preview org, you can enter the URL for your Okta Preview Sandbox org (for example, https://mycompany.oktapreview.com).
- Click Next to continue to an Okta Sign In page.
- Sign in to the service-specific Okta account.
- Click Allow Access.
- Click Finish to complete the installation.
If during the agent installation you encounter Error code 12: Could not establish trust relationship for the SSL/TLS service channel, ensure that you are running the latest version of the agent as older agent versions do not support TLS 1.2.
- Configure a RADIUS app in Okta, which includes the RADIUS agent port, shared secret, and advanced RADIUS settings. For more information about configuring RADIUS apps, see RADIUS applications in Okta
Additional Property Configurations
You can override the defaults on the following properties, if desired.
Changes to the RADIUS Agent config.properties file are only loaded on agent restart. Always restart your agent after changing config.properties.
- Open the folder where the Okta RADIUS agent resides. The default installation folder is C:\Program Files (x86)\Okta\Okta RADIUS Agent\.
- From this folder, navigate to current\user\config\radius\config.properties. Create a backup of this file and then open the original in a text editor.
- Configure any of the properties shown below, as required.
- When done, save the file.
- Changes are effective after restarting the Okta RADIUS Agent service using the available Windows administrative tools.
Property Description Default ragent.num_max_http_connection The maximum number of HTTP connections in the connection pool. 20* ragent.num_request_threads The number of authentication worker threads available for processing requests. 15* ragent.total.request.timeout.millisecond The maximum time the RADIUS agent is allowed to process a UDP packet after it has arrived from the RADIUS client.
For the Okta Verify with Push factor, the actual value is interpreted by the RADIUS agent as one half (1/2) of the configured value.
For example: 60000 = 60 seconds, divided in half = 30 seconds.
For all other factors the value is used as specified.
60000 ragent.request.timeout.millisecond The maximum time the RADIUS agent is allowed to process a UDP packet after it has arrived from the RADIUS client.
If specified, ragent.total.request.timeout.millisecond is ignored.
If not specified, the default is to use ragent.total.request.timeout.millisecond.
Available since version 2.9.4.
N/A defaults to value specified by ragent.total.request.timeout.millisecond ragent.okta.request.max.timeout.millisecond The socket timeout to set on the Okta API request. This property only applies if configured; otherwise, it is computed dynamically based on the total request timeout setting. Dynamic, based on remaining TTL for request ragent.request.timeout.response.mode The timeout response mode. Possible values include:
- SEND_REJECT_ALWAYS: agent sends a reject message to the client after any timeout.
- SEND_REJECT_ON_POLL_MFA: agent sends a reject message to the client if a timeout occurs during the MFA polling loop only (that is, while the agent is polling Okta to determine if the user has correctly responded to an MFA challenge such as a push notification). If a timeout occurs at any other time, no response will be sent to the client.
- NO_RESPONSE: no response will be sent to the client when the agent times out.
SEND_REJECT_ON_POLL_MFA ragent.mfa.timeout.seconds Time, in seconds, that the agent will wait for the client to respond to an MFA challenge such as factor selection. 60
* If "Request queue is full" appears in your logs, the RADIUS Server Agent is rejecting login attempts due to reaching the maximum number of threads and connections that it can process. See Request queue is full.
When using the RADIUS agent with a VPN, such as Cisco ASA VPN, the following timeout values should be configured on both RADIUS Agent and VPN settings:
RADIUS agent v2.9.3 and earlier without Okta Verify Push. ragent.total.request.timeout.millisecond = VPN retry count * (VPN timeout + VPN wait between retries) - VPN wait between retries RADIUS agent v2.9.3 with Okta Verify Push. ragent.total.request.timeout.millisecond = 2 * (VPN retry count * (VPN timeout + VPN wait between retries) - VPN wait between retries) RADIUS agent v 2.9.4 and later. ragent.request.timeout.millisecond = VPN retry count * (VPN timeout + VPN wait between retries) - VPN wait between retries
- VPN retry count should be between 3-5.
- VPN request timeout should be 15-60s, (60-120s when using Okta Verify Push).
For example, where:
- VPN retry = 5x
- VPN request timeout = 60s
- VPN wait between retry = 5s
Then, VPN authentication timeout = 5 * (60 + 5) - 5 = 320s, or 320000ms
RADIUS agent v2.9.3 and earlier with Okta Verify Push: ragent.total.request.timeout.millisecond = 320000.
RADIUS agent v 2.9.4 and later: ragent.request.timeout.millisecond = 320000.
The following properties apply to proxy configuration only:
Property Description Default ragent.proxy.enabled Indicates whether the RADIUS agent should use a proxy. Set to true. For example,
ragent.proxy.enabled = true
Not present. Add this property to config.properties. ragent.proxy.address The IP address (and port, if required), of the proxy. This property must exist when ragent.proxy.enabled is true. For example,
ragent.proxy.address = 127.0.0.1:8888
Not present. Add this property to config.properties.
ragent.ssl.pinning If the proxy terminates the SSL connection, disable SSL pinning. For example,
ragent.ssl.pinning = false
Proxy credentials, if required. Encrypted on agent restart. For example,
ragent.proxy.user = adminragent.proxy.password = password
Not present. Add this property to config.properties.
For a complete list of all steps as well as detained steps for installing the Okta RADIUS agent see: