Citrix ADC (formerly Citrix Netscaler) is an application delivery and load balancing solution (see https://www.citrix.com/products/citrix-adc/). This integration provides instructions to integrate Citrix ADC with Identity as a Service. Once integrated, users can use single sign-on to log in to their Citrix ADC account using Identity as a Service
Note: This guide was tested using previous versions of Identity as a Service and Citrix ADC. Other versions of Citrix ADC may require integration and configuration steps that differ from those documented in this procedure. For newer versions of Citrix ADC, this integration guide may be used as an initial approach for integrating Citrix ADC. In the event of other issues, contact support@entrust.com for assistance.
Add Citrix ADC to Identity as a Service
1. Log into your Identity as a Service administrator account.
2. Click
> Security > Applications. The Applications
Lists page appears.
3. Click Add. The Select an Application Template page appears.
4. Do one of the following:
● Select SAML Cloud Integrations from the search drop-down list and scroll to find the application you want to add to IDaaS.
- or -
● In the Search bar, enter a search option to filter for the application you want to add to IDaaS.
5. Click Citrix. The Add Citrix page appears.
6. In the Application Name field enter Citrix ADC.
7. Enter an Application Description.
8. Optional. Add a custom application logo.
a. Click next to Application Logo. The
Upload Logo dialog box appears.
b. Click to
select an image file to upload.
c. Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
d. If required, resize your image.
e. Click OK.
9. Select the Authentication Flow that appears to users during login.
10. Click Next. The General page appears.
11. If available, use the Upload Metadata XML file option to auto-populate the following fields, if available in the file:
● Default Assertion Consumer Service URL
● Alternative Assertion Consumer URLs
● Service Provider Entity ID (Issuer)
● Single Logout Service URL
● SAML Signing Certificate
● SAML NameID Encoding Format
● SAML Signature Algorithm
12. To import the Metadata file:
a. Click and browse
to select the file. The Metadata
Configuration dialog box appears.
b. If required, click Merge with existing values to merge new values with existing values for Alternative Assertion Consumer Services URLs and SAML attribute names.
c. Click Save.
13. Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
14. Enter the Max Authentication Age (seconds) to set the maximum amount of time that can elapse before a user is required to reauthenticate during a new login attempt. This applies for both SP-initiated and IDP-initiated login. Set this field to -1 to disable this feature.
15. If you do not have a metadata file, use the information provided in the next steps to populate the fields.
a. Enter the Default Assertion Consumer Service URL for the application.
Example: https://<server.domain.com>/cgi/samlauth
b. Enter the Service Provider Entity ID (Issuer) that is used by Identity as a Service to identify your application.
Example: <server.domain.com>
16. Optional. Enter the SAML Username Parameter Name used to identity the user ID being requested for authentication. The user ID can then be passed as a parameter, for example, Username=jdoe.
17. From the SAML Name ID Attribute drop-down list, select the User ID.
18. Select the SAML Signing Certificate from the drop-down list.
19. From the SAML NameID Encoding Format from the drop-down list, select UNSPECIFIED.
20. From the SAML Response Signature Algorithm drop-down list, select SHA256.
Note: Citrix ADC cannot accept signed responses using a SHA512 signature algorithm.
21. Optional: Select Sign complete SAML response to ensure the message integrity of the SAML response sent to the application during authentication.
22. Optional: Select Respond Immediately for Unsuccessful Responses to return to the application immediately after a login failure, rather than allow user to try again with a different userID.
23. Deselect Enable Go Back Button if you do not want users to be able to go back to the Citrix ADP login page to log in.
24. Select Show Default Assertion Consumer URL Service in the My Profile. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.
25. Optional: Select Encrypt SAML Assertion. When selected the SAML Assertion is also encrypted. If you select this option, do the following:
a. From the Encryption Method for Key drop-down list, select either RSA Version 1.5 or RSA-OAEP. RSA Version 1.5 is the default.
b. From the Encryption Method for Data drop-down list, select the encryption method used to encrypt data. The options are:
– AES-256 (default)
– AES-128
– AES-192
– Triple DES
26. In the Encryption Certificate field, upload the encryption certificate file.
Note: The Subject Domain Name and Certificate Expiry Date values are populated with values from the certificate once the Encryption Certificate is uploaded.
27. Optional. Add Alternative Assertion Consumer Service URLs, as follows:
a. Click Add.
b. Enter a Name.
c. Enter a URL Value.
d. Select Show in My Profile to display the Alternative Consumer Service URL in a user's My profile page.
e. Optional. Add an Application Logo.
f. Click Add.
g. Repeat these steps to add more Alternative Assertion Consumer Service URLs.
28. Optional. Add a Relay State as follows:
a. Under Relay State, click Add. The Add Relay State dialog box appears.
b. Enter a Name for the relay state.
c. Enter the Value for the relay state. This setting specifies the application or URL that is a user is redirected to after successful authentication.
d. Select Show in My Profile to display the relay state on the user's My Profile page.
Note: After
you add relay states, you can also enable or disable them on the Add/Edit
application page. Click
next to the relay state to disable it or click
to re-enable it.
Relay states apply to the Default Assertion Consumer Service URLs and
not the Alternative Assertion Consumers URLs.
e. Optional.
Add a Relay State custom logo.
Click next
to Relay State Logo. The Upload
Logo dialog box appears.
Click
to select an image file to upload.
Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
If required, resize your image.
Click OK.
f. Click Add.
g. Repeat these steps to add more Relay States.
29. Click Submit.
Download the Metadata file from Identity as a Service
1. In Identity as a Service, click
> Security > Applications.
The Applications List page appears.
2. Do one of the following:
● Click
next to the application you are integrating
with Identity as a Service.
–or–
● Click
next to the application you are integrating
with Identity as a Service and select SAML IDP Metadata.
The SAML Application Metadata dialog box appears.
3. Select the certificate to include in the SAML IDP Metadata file from the drop-down list.
4. If applicable, Select the domain to include in the SAML IDP Metadata file from the drop-down list.
5. Enter the Lifetime, in days, for the SAML IDP Metadata file. The value must be between 2 and 730.
6. Do one of the following, as required:
a. Copy the Public Endpoint to paste into your SAML application being used Identity Provider authentication.
b. Click Download.
Note: If you are using multiple domains, you must download each domain's metadata file separately because the values in the metadata file vary for each domain.
Export a SAML signing certificate
1. Log in to your Identity as a Service administrator account.
1. Click
> Security > Applications.
The Applications List page appears.
2. Under SAML Cloud Integrations, click SAML Signing Certificates. The SAML Signing Certificates page appears.
3. Click
next to the certificate to export the certificate
you want to import into your SAML service provider application. The Export Certificate dialog box appears.
a. If the certificate has been issued by a CA, do one of the following:
– Click Certificate to export the self-signed certificate.
– Click Root CA Certificate to export a certificate issued from a CA.
– Click Certificate Chain to export the SAML signing certificate and its CA certificates.
b. Click Export.
1. In the Citrix ADC Configuration menu, expand Traffic Management > SSL > Certificates > CA Certificates.
Note: Even though the SAML IDP signing certificate is not a CA certificate, for NetScaler version 11.1+, you must import it under CA Certificates.
2. On the CA Certificates page, click Install.
3. On the Install Certificates section, under Certificate-Key Pair Name, enter a descriptive name for the SAML IDP signing certificate, for example <domain>.us.trustedauth.com.
4. Under Certificate File Name click Browse and select the certificate file you downloaded in Step 4: Download the SAML signing certificate.
5. Leave the Key File Name field empty.
6. Click Install.
1. In the Citrix ADC Configuration menu, expand NetScaler Gateways > Policies > Authentication> SAML. The SAML server page appears.
2. On the SAML page, click the Servers tab.
3. On the Servers tab, click Add.
4. On the Create Authentication SAML Server page, enter the following information:
Field |
Description |
Value Example |
Name |
Descriptive name for the IDP |
Identity as a Service |
IDP Certificate Name |
The SAML signing certificate from the Identity as a Service IDP. |
The SAML signing certificate you downloaded in Step 4: Download the signing certificate. |
Redirect URL |
The location of the SAML servlet in Identity as a Service, extracted from the IDP metadata file. |
https://<domain>.us.trustedauth.com/api/saml/SAML2/SSO |
Single Logout URL |
The single logout URL. |
https://<domainFQDN>/cgi/saml/tmlogout |
User Field |
The user identifier from the IDP metadata file. It should be Name ID in most cases. |
Name ID |
Signing Certificate Name |
The SP SAML signing certificate. |
This should already exist in Identity as a Service. |
Issuer Name |
The entityID of the SAML SP. |
This value should match the Service Provider ID (Issuer) you entered in Step 1: Add Citrix NetScaler to Identity as a Service. |
Reject Unsigned Assertion |
ON = Reject the Identity as a Service Assertion if it is not signed. OFF = Accept the Identity as a Service assertion if is not signed. |
ON |
SAML Binding |
The binding method for SAML assertion. This must be POST. |
POST |
5. Click Create.
1. In Citrix ADC Configuration menu, expand NetScaler Gateways> Policies> Authentication> SAML. The SAML server page appears.
2. On the SAML page, click the Policies tab.
3. On the Policies tab, click Add.
4. On the Create Authentication SAML Policy page, under Name enter a descriptive name for the SAML Policy, for example Identity as a Service Policy.
5. From the Server drop-down list, select the SAML Authentication Server that you created in Step 6: Add a SAML authentication server to Citrix NetScaler.
6. Under Expression, click the empty text box under the Operators button and enter ns_true.
Note: A setting of ns_true means that the policy is always active when assigned to a VIP. This is an example of a very basic policy settings. The policy may be further fine-tuned in accordance with the Ctirix product documentation and the Ctirix Customer Support team if required.
7. Click Create.
8. In the Citrix NetScaler Configuration menu, expand NetScaler Gateways > Virtual Servers. The NetScaler Gateway Virtual Servers page appears.
9. Under the Name column, click the name of the virtual server that requires the Identity as a Service Policy to be added.
10. On the VPN Virtual Server page, under Basic Authentication, click the + icon.
11. On the Choose Type pane, under Choose Policy select SAML.
12. Under Choose Type, select Primary.
13. Click Continue.
14. In the Policy Binding section under Select Policy, click the > button to access the SAML Policies page.
15. On the SAML Policies page, click the radio button to select the policy you created in Step 6: Add a SAML authentication server to Citrix NetScaler, for example Identity as a Service Policy, and then click Select.
16. Under Binding Details, enter 100 for the Priority.
17. Click Bind.
Note: If additional Primary Authentication policies exist, they may need to be unbound if it is to be enforced that only the SAML IDP should be used for authentication.