Configure NetMotion Mobility to interoperate with Okta via RADIUS

This guide details how to configure NetMotion mobility to use the Okta RADIUS Server Agent in conjunction with the Okta Integration Network (OIN) NetMotion Moblity (RADIUS) app.

Topics

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
HTTP
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)

Supported Factors

The following MFA Factors are supported:

Important Note

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

MFA Factor Password Authentication Protocol
PAP
Extensible Authentication Protocol - Generic Token Card
EAP-GTC
Extensible Authentication Protocol - Tunneled Transport Layer Security
EAP-TTLS
Custom TOTP Authentication Supported Supported Supported
Duo(Push, SMS and Passcode only) Supported Not supported Not supported

Email

Supported

Supported

Not supported

Google Authenticator Supported Supported Supported - as long as challenge is avoided.
For example MFA only or password, MFA.

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 auth + MFA as the push challenge is sent out-of-band.

RSA Token

Supported

Supported

Supported

Security Question

Supported Supported Not supported
SMS authentication Supported Supported Not supported
Symantec VIP Supported Supported Supported

Voice Call

Supported Supported Not supported

YubiKey

Supported Supported Supported
Caution

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

Info

Note

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.

Typical workflow

Perform the following tasks, in the order shown:

Task

Description

Download the RADIUS agent
  • Download the Okta RADIUS Agent from the Settings > Downloads page your in Okta org. Note that there are both Windows and Linux agents
Install the Okta RADIUS Agent.
Configure application
Configure NetMotion with the RADIUS settings
Add Trusted root CA
Verify Connection
  • Ensure that the end-user’s NetMotion Mobility client has the right server settings.
    For example:


Related topics