Citrix Gateway supported versions, clients, features and factors
The Citrix Gateway supports the following versions, clients, features and factors.
Supported Versions
This guide has been verified with the following Citrix Gateway versions:
- Version 10.5.x
- Version 11.x
- Version 12.x
- Version 13.0.x
Supported Clients
The following Citrix clients have been validated:
- Citrix Web Receiver
- Citrix Windows \ Mac Receiver
- Citrix iOS \ Android Receiver
Supported features
The following Okta features are supported:
- Authentication with Okta Credentials via RADIUS
- Authentication with Okta Credentials via SAML
- Multi-factor authentication via RADIUS
- Multi-factor authentication via SAML
- Group memberships/Attributes via RADIUS – passes the username and password to storefront for AD group permissions
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 |
Duo(Push, SMS and Passcode only) | Supported | Not supported | Not supported |
Supported |
Supported |
Not supported |
|
Supported | Supported | Supported - as long as challenge is avoided. For example MFA only or password, MFA. |
|
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. |
|
Not supported |
Not supported |
Not supported |
|
Supported |
Supported |
Supported |
|
Supported | Supported | Not supported | |
SMS authentication | Supported | Supported | Not supported |
Symantec VIP | Supported | Supported | Supported |
Supported | Supported | Not supported | |
Supported | Supported | Supported |
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.