Push notification for OTP
Citrix Gateway supports push notifications for OTP. Users do not have to manually enter the OTP received on their registered devices to log in to Citrix Gateway. Admins can configure Citrix Gateway such that login notifications are sent to users’ registered devices using push notification services. When users receive the notification, they have to simply tap Allow on the notification to log in to Citrix Gateway. When gateway receives acknowledgment from the user, it identifies source of the request, and sends response to that browser connection.
If the notification response is not received within the timeout period (30 seconds), users are redirected to the Citrix Gateway login page. The users can then enter the OTP manually or click Resend Notification to receive the notification again on the registered device.
Admins can make push notification authentication as the default authentication by using the login schemas created for push notification.
Push notification feature is available with a Citrix ADC Premium edition license.
Advantages of push notifications
- Push notifications provide a more secure multifactor authentication mechanism. Authentication to Citrix Gateway is not successful until the user approves the login attempt.
- Push notification is easy to administer and use. Users have to download and install the Citrix SSO mobile app that does not require any administrator assistance.
- Users do not have to copy or remember the code. They have to simply tap on the device to get authenticated.
- Users can register multiple devices.
How push notifications work
The push notification workflow can be classified into two categories:
- Device registration
- End user login
Prerequisites for using push notification
Complete the Citrix Cloud onboarding process.
Create a Citrix Cloud company account or join an existing one. For detailed processes and instructions on how to proceed, see Signing Up for Citrix Cloud.
Log in to https://citrix.cloud.com, and select the customer.
From Menu, select Identity and Access Management and then navigate to API Access tab to create a client for the account.
Copy the ID, secret, and customer ID. The ID and secret are required to configure push service in Citrix ADC as “ClientID” and “ClientSecret” respectively.
- Same API credentials can be used on multiple data centers.
- On premises Citrix ADC appliances must be able to resolve server addresses mfa.cloud.com and trust.citrixworkspacesapi.net and are accessible from the appliance. This is to ensure that there are no firewalls or IP address blocks for these servers over port 443.
Download the Citrix SSO mobile app from App Store and Play Store for iOS devices and Android devices respectively. Push notification is supported on iOS from build 1.1.13 on Android from 2.3.5.
Ensure the following for the Active Directory.
- Minimum attribute length must be at least 256 characters.
- Attribute type must be ‘DirectoryString’ such as UserParameters. These attributes can hold string values.
- Attribute string type must be Unicode, if device name is in non-English characters.
- Citrix ADC LDAP administrator must have write access to the selected AD attribute.
- Citrix ADC and the client machine must be synchronized to a common Network Time Server.
Push notification configuration
The following are the high-level steps that must be completed to use the push notification functionality.
The Citrix Gateway administrator must configure the interface to manage and validate users.
Configure a push service.
Configure Citrix Gateway for OTP management and end user login.
Users must register their devices with gateway for logging in to Citrix Gateway.
Register your device with Citrix Gateway.
Log in to Citrix Gateway.
Navigate to Security > AAA-Application Traffic > Policies > Authentication > Advanced Policies > Actions > Push Service and click Add.
In Name, enter the name of the push service.
In Client ID, enter the unique identity of the relying party for communicating with Citrix Push server in cloud.
In Client Secret, enter the unique secret of the relying party for communicating with Citrix Push server in cloud.
In Customer ID, enter the customer ID or name of the account in cloud that is used to create Client ID and Client Secret pair.
The TLS 1.2 version is required for push service. For more information, see TLS 1.2 configuration details.
Complete the following steps for OTP management and end user login.
- Create login schema for OTP management
- Configure authentication, authorization, and auditing virtual server
- Configure VPN or load balancing virtual servers
- Configure policy label
- Create login schema for end user login
For details on configuration, see Native OTP support.
Important: For push notification, admins must explicitly configure the following:
- Create a push service.
- While creating login schema for OTP management, select the SingleAuthManageOTP.xml login schema or equivalent as per the need.
- While creating login schema for end user login, select the DualAuthOrPush.xml login schema or equivalent as per the need.
Users must register their devices with Citrix Gateway to use the push notification functionality.
In your web browser, browse to your Citrix Gateway FQDN, and suffix /manageotp to the FQDN.
This loads the authentication page. Example: https://gateway.company.com/manageotp
Log in using your LDAP credentials or appropriate two-factor authentication mechanisms, as required.
Click Add Device.
Enter a name for your device, then click Go.
A QR code is displayed on the Citrix Gateway browser page.
Scan this QR code using the Citrix SSO app from the device to be registered.
Citrix SSO validates the QR code and then registers with gateway for push notifications. If there are no errors in the registration process, the token is successfully added to the password tokens page.
If there are no additional devices to add/manage log out using the list at the top right corner of the page.
To test the OTP, click your device from the list and then click Test.
Enter the OTP that you have received on your device and click Go.
The OTP verification successful message appears.
Log out using the list at the top right corner of the page.
Note: You can use the OTP management portal anytime to test authentication, remove registered devices, or register more devices.
After registering their devices with Citrix Gateway, users can use the push notification functionality for authentication.
Navigate to your Citrix Gateway authentication page (for example: https://gateway.company.com)
You are prompted to enter only your LDAP credentials depending on the login schema configuration.
Enter your LDAP user name and password, then select Submit.
A notification is sent to your registered device.
Note: If you want to enter the OTP manually, you must select Click to input OTP manually and enter the OTP in the TOTP field.
Open the Citrix SSO app on your registered device and tap Allow.
In case of an iOS device, you are prompted for Touch-ID/Face-ID/Passcode as an extra factor of authentication.
The authentication server waits for push server notification response until the configured timeout period expires. After the timeout, Citrix Gateway displays the login page. The users can then enter the OTP manually or click Resend Notification to receive the notification again on the registered device. Based on your selected option, gateway validates the OTP that you have entered or resends the notification on your registered device.
- No notification is sent to your registered device regarding login failure.
- The device registration might fail in the following cases.
- Server certificate might not be trusted by end-user device.
- Citrix Gateway used to register for OTP is not reachable by client.
- The notifications might fail in the following cases.
- User device is not connected to the internet
- Notifications on the user device are blocked
- User does not approve the notification on the device
In these cases, the authentication server waits until the configured timeout period expires. After the timeout, the Citrix Gateway displays a login page with the options to manually enter the OTP or to resend the notification again on your registered device. Based on the selected option, further validation occurs.
The following are the expected logs when the OTP push service is not reachable.
- Push notification failure when user device is not connected to the internet - Push: Failed to prepare Push Request to “
client name” for Push service.
- Device registration failure log - Push: No devices are registered to send Push Request to cloud for “
- In case user does not accept the push - Push: Response is not seen from client, for “
user name”, checking retry options.
Citrix SSO app behavior on iOS – points to note
Citrix SSO iOS app includes support for actionable notifications to enhance user experience. Once a notification is received on an iOS device, and if the device is locked or the Citrix SSO app is not in foreground, users can use the shortcuts built into the notification to either approve or deny login request.
To access notification shortcuts, users need to either force touch (3D touch) or long press the notification depending on the device’s hardware. Selecting the Allow shortcut action sends a login request to Citrix ADC. Depending on how the authentication policy is configured on the authentication, authorization, and auditing virtual server;
- The login request might be sent in the background without any need to launch the app into foreground or unlock the device.
- The app might prompt for Touch-ID/Face-ID/Passcode as an extra factor in which case the app is launched into foreground.
To delete a password token registered for push in the Citrix SSO app, users must perform the following steps:
- Unregister (remove) the iOS/Android device on gateway. QR code for removing registration from device appears.
- Open the Citrix SSO app and tap the info button of the password token to be deleted.
- Tap Delete Token and scan the QR code.
- If the QR code is valid, the token is successfully removed from the Citrix SSO app.
- Users can tap Force Delete to delete a password token without having to scan the QR code if the device is already removed from gateway. Force deleting might result in the device continuing to receive notifications if the device has not been removed from Citrix Gateway.