This article describes how to integrate RSA with Citrix NetScaler using SAML IDR SSO.
Configure RSA Cloud Authentication Service
Perform these steps to configure RSA Cloud Authentication Service as an SSO Agent SAML IdP to Citrix NetScaler.
Procedure
- Sign in to RSA Cloud Administration Console and browse to Applications > Application Catalog.
- Search for Citrix NetScaler and click Add to add the connector.
- On the Basic Information page, choose Identity Router.
- Enter a name for the application and click Next Step.
- On the Connection Profile page, navigate to the Initiate SAML Workflow section.
- Choose IdP-initiated.
- Scroll down to the Identity Provider section. Note the Identity Provider URL needed for the Citrix NetScaler configuration.
- Identity Provider URL is automatically generated.
- Identity Provider Entity ID is automatically generated.
- Import a private/public key pair to sign and validate SAML assertions. If you do not have one readily available, follow the steps to generate a certificate bundle. Otherwise, continue to the next step. Make a note of the certificate and private key as they are required for the Citrix NetScaler configuration.
- In the SAML Response Signature section, click Generate Certificate Bundle.
- Enter a common name for your Identity Router domain in the Common Name (CN) field.
- Click Generate and Download, save the certificate bundle ZIP file to a secure location, and extract its contents. The ZIP file contains a private key, a public certificate, and a certificate signing request.
- Scroll down to the Service Provider section and enter the following details:
- ACS URL: The format is https://<ns_vs_hostname>/cgi/samlauth. Replace <ns_vs_hostname> with the hostname or IP address of your NetScaler virtual server, which can be obtained from the Citrix NetScaler configuration.
- Audience (Service Provider Entity ID): The format is https://<ns_vs_hostname>. Replace <ns_vs_hostname> with the hostname or IP address of your NetScaler virtual server, which can be obtained from the Citrix NetScaler configuration.
- Scroll down to the User Identity section and select the following:
- Identifier Type – Email Address
- Identity Source – Select your user identity source
- Property – mail
- Click Next Step.
- On the User Access page, select the access policy that the identity router will use to determine which users can access the application.
- Click Next Step.
- On the Portal Display page, configure the portal display and other settings.
- Click Save and Finish.
- Click Publish Changes and wait for the operation to be completed.
After publishing, your application is now enabled for SSO.
Configure Citrix NetScaler
Perform these steps to configure Citrix NetScaler.
Procedure
- Log on to the Citrix NetScaler Gateway web administration console.
- Browse to Configuration > NetScaler Gateway > Policies > Authentication > SAML and click Add.
- Enter a name for the SAML Authentication Policy and click Add next to the Server drop-down menu.
- Configure the SAML Authentication Server settings and click Create.
- Enter a Name for the Authentication SAML Server.
- In the Redirect URL field, enter the Identity Provider URL that was provided in the RSA Cloud Authentication Service configuration.
- In the IDP Certificate Name drop-down list, select the public certificate provided in the RSA Cloud Authentication Service configuration. If you have not added the certificate yet, refer to the steps in the Notes section to add it.
- Type mail in User Field.
- On the SAML Authentication Policy page, type ns_true in the Expression field and click Create.
- Navigate to Configuration > NetScaler Gateway > Virtual Servers.
-
Take note of the Name and IP Address of the NetScaler Virtual Server. These are needed for the RSA Cloud Authentication Service configuration.
-
Click to edit the NetScaler Gateway Virtual Server.
-
Click + to bind a Basic Authentication policy.
-
Select SAML Policy and Primary Type and click Continue.
-
Click > icon to select the policy.
-
Select the authentication policy that was configured earlier to bind it and click Select.
-
Set the Priority and click Bind.
-
Click Done.
The configuration is complete.
Notes
In the NetScaler Gateway web administration console, you may not have a NetScaler virtual server initially. In this case, you will need to create your virtual server, assign it a preferred name, and assign an IP address.
You can configure as many virtual servers as necessary, but ensure that the state of the virtual server is set to Up for proper functionality.
If you need to add a public certificate, follow these steps:
- Navigate to Traffic Management > SSL > Certificates.
- Click Install.
- Enter a name for the certificate-key pair.
- Click Choose File next to the certificate file name field. A file browser appears, allowing you to select and upload your certificate file. The public certificate file should be of the .cert type.
- Select the file and click Open to confirm.
- If you have a private key, repeat the same steps for the private key file. This field is optional and hence you may not have a private key to upload.
- Set the Certificate Format to PEM.
- Click Install.
Your certificate is added and available for future use.
Return to Citrix NetScaler - RSA Ready Implementation Guide.
Related Articles
Citrix ShareFile - RSA Ready Implementation Guide 13Number of Views Citrix Cloud - RSA Ready Implementation Guide 26Number of Views Citrix NetScaler - SAML Relying Party Configuration - RSA Ready Implementation Guide 5Number of Views Citrix NetScaler - SAML My Page SSO Configuration - RSA Ready Implementation Guide 5Number of Views Citrix NetScaler - RSA Ready Implementation Guide 27Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA SecurID Software Token 5.0.2 for Windows Desktop displays message after reboot due to roaming profile: No token stor…