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 authenticators are supported:

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

MFA Authenticator 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.

RADIUS does not 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 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

Phone (SMS and Voice call)

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

YubiKey(OTP only)

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

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.