Configure Fortinet Appliance

Meet the following network connectivity requirements before you install the Okta RADIUS agent:

Source	Destination	Port/Protocol	Description
Okta RADIUS Agent	Okta Identity Cloud	TCP/443 HTTP	Configuration and authentication traffic.
Client Gateway	Okta RADIUS Agent	UDP/1812 RADIUS (Default, you can change this when you install and configure the RADIUS app)	RADIUS traffic between the gateway (client) and the RADIUS agent (server).

Limitations

If you've migrated a RADIUS-configured org from Classic Engine and you configure the Okta Verify authenticator with the number challenge, the challenge may be presented to RADIUS users even though it's not supported. To prevent this, enable the Early Access feature Disable number matching challenge for RADIUS. See Manage Early Access and Beta features.

Supported factors

The size of the challenge message can be too large for the RADIUS prompt if you let users enroll too many authenticators. Okta recommends that you enroll no more than eight authenticators at a given time.

Okta supports the following authenticators for RADIUS apps:

MFA Authenticator	Password Authentication Protocol (PAP)	Extensible Authentication Protocol - Generic Token Card (EAP-GTC)	Extensible Authentication Protocol - Tunneled Transport Layer Security (EAP-TTLS)
Duo(Push, SMS, and Passcode only)	Supported	Supported	Duo passcode only.
Email	Supported	Supported	Supported when the string "EMAIL" is initially sent. Refer to associated note.
RADIUS doesn't 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 (for one device only)	Supported (for one device only)	Supported (for one device only), 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 the string "CALL" is sent. Refer to 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 the user is prompted to select factors to complete the authentication.
• MFA Only: Instead of password, users 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”.

Protocols support the following authentication methods:

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".