Pulse Connect Secure supported versions, and factors

The Pulse Connect Secure supports the following versions, clients, features and factors.

Supported Versions

This guide has been verified with the following versions:

  • Pulse Connect Secure v8.3

Supported factors

The following MFA factors are supported:

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 - as long as challenge is avoided.
For example MFA only or "Password, passcode".
Duo(Push, SMS and Passcode only) Supported Supported Duo passcode only.

Email

Supported

Supported

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

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

RSA Token/ On-prem MFA

Supported

Supported

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

Security Question

Supported (Password and MFA only) Supported (Password + MFA only).
Not supported
SMS authentication Supported Supported
Supported when string "SMS" is sent.
See associated note.
Symantec VIP Supported Supported Supported - as long as challenge is avoided.
For example MFA only or "Password, passcode".

Voice Call

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

YubiKey

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

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.