Configure BeyondTrust to interoperate with Okta via RADIUS

Okta and BeyondTrust interoperate through either RADIUS or SAML 2.0. For each Password Safe deployment, you can assign one or more authentication providers. Each RADIUS authentication profile maps to to a group of users via a filter (All Users, All Local Users, All Domain Users, Domain Contains, etc). Using RADIUS, Okta’s agent translates RADIUS authentication requests from BeyondInsight, the BeyondTrust web application and console, into Okta API calls.

This guide details how to configure BeyondTrust PowerBroker Password Safe to use the Okta RADIUS Server Agent.


Before you begin

Before installing the Okta RADIUS Agent ensure that you have met these minimum requirements for network connectivity:

Source Destination Port/Protocol Description
Okta RADIUS Agent Okta Identity Cloud TCP/443
Configuration and authentication traffic
Client Gateway Okta RADIUS Agent UDP/1812 RADIUS (Default, may be changed in RADIUS app install and configuration) RADIUS traffic between the gateway (client) and the RADIUS Agent (server)


Only a single Okta Verify device should be enrolled. Enrolling second and subsequent Okta Verify devices may cause undefined or unexpected behavior.

Supported factors

The following MFA authenticators are supported:

When integrating with Okta RADIUS, the maximum supported number of enrolled authenticators is dependent on the size of resulting challenge message. Okta recommends that no more than eight (8) be enrolled at one time.

MFA Authenticator Password Authentication Protocol
Extensible Authentication Protocol - Generic Token Card
Extensible Authentication Protocol - Tunneled Transport Layer Security
Custom TOTP Authentication Supported Supported Supported - as long as challenge is avoided.
For example MFA only or "Password, passcode".
Duo(Push, SMS and Passcode only) Supported Supported Duo passcode only.




Supported when string "EMAIL" is initially sent.
See associated note.

RADIUS does not support inline enrollment with Email. When using inline enrollment, either disable Email or specify Password reset in Email settings.

Google authenticator

Supported Supported Supported - as long as challenge is avoided.
For example MFA only or "Password, passcode".

Okta Verify (TOTP and PUSH)

Supported Supported Supported - as long as challenge is avoided.
For example:
MFA-only or "Password, MFA" for TOTP.
Push can work with primary authentication with MFA as the push challenge is sent out-of-band.

Okta Verify (number challenge)

Not supported

Not supported

Not supported

Phone (SMS and Voice call)

Supported Supported Supported when string "CALL" is sent.
See associated note.

YubiKey OTP

Supported Supported Supported - as long as challenge is avoided.
For example MFA only or "Password, passcode".

RADIUS supports three authentication methods:

  • Password + MFA: Primary authentication using password, then user is prompted to select factors to complete the authentication.
  • MFA Only: Instead of password, user enter either One Time Passcode, or one of “EMAIL”, “SMS”, “CALL”, “PUSH” (case insensitive).
  • Password,Passcode: Password entered immediately followed by passcode in a request.
    Must be in the same request, for example: Abcd1234,879890” or “Abcd1234,SmS”.

The following authentication methods are supported by protocol:

Protocol Supports
PAP Password and MFA, MFA, "Password and passcode".
EAP-TTLS MFA only, "Password and passcode".
EAP-GTC Password and MFA, MFA only, "Password and passcode".

Must send the specified the string “EMAIL/SMS/CALL”, which will initially return a failure, but will result in the generation of an One Time Passcode(OTP) provided using the specified method. The provided OTP can then be used for authentication.

EAP-TTLS does not support enrollment

Authentication will fail unexpectedly when EAP-TTLS is enabled, either Okta Verify or Phone are specified as required enrollment policy, and the user is not enrolled in that authenticator.

The U2F Security and Windows Hello MFA factors are not compatible with RADIUS-enabled implementations.
For additional information about the RADIUS apps refer to Configuring RADIUS applications in Okta.

Passwordless authentication

RADIUS authentication uses passwords as the primary authentication mechanism. Traditional RADIUS authentication cannot be performed with passwordless users. RADIUS can use other factors for authentication when the application setting property Okta performs primary authentication is unchecked. See2FA Only (Passwordless Mode) in RADIUS applications in Okta for addition detail.

For more information on passwordless authentication see Set up passwordless sign-in experience.

Typical workflow



Download the RADIUS agent
Install the Okta RADIUS Agent.
  • Install either the Windows or Linux RADIUS agents as appropriate for your environment.
Configure application
Configure optional settings
Configure gateway

Related topics