Palo Alto Networks supported features and factors
Palo Alto Networks supports the following versions, clients, features and factors.
Supported features
The following Okta features are supported:
Feature | Supported |
Notes |
---|---|---|
Authentication with Okta Credentials via RADIUS | Yes |
|
Authentication with Okta Credentials via SAML. |
No |
The RADIUS Integration for Palo Alto VPN does not support SAML. |
Multi-factor authentication via RADIUS | Yes |
|
Multi-factor authentication via SAML | Yes |
The RADIUS Integration for Palo Alto VPN does not support MFA using SAML. |
Supported factors
The following MFA
When integrating with Okta RADIUS, the maximum supported number of enrolled
MFA |
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. |
Supported |
Supported |
Supported when string "EMAIL" is initially sent. |
|
Supported | Supported | Supported - as long as challenge is avoided. For example MFA only or "Password, passcode". |
|
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. |
|
Not supported |
Not supported |
Not supported |
|
RSA Token/ On-prem MFA |
Supported |
Supported |
Supported - as long as challenge is avoided. |
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". |
Supported | Supported | Supported when string "CALL" is sent. See associated note. |
|
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
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.