Zendesk for Service - SAML Relying Party Configuration - RSA Ready Implementation Guide
Originally Published: 2023-08-23
This section describes how to integrate RSA Cloud Authentication Service with Zendesk for Service using SAML Relying Party.
Configure RSA Cloud Authentication Service
Perform these steps to configure RSA Cloud Authentication Service as a Relying Party to Zendesk for Service.
Procedure
- Sign in to RSA Cloud Administration Console.
- Click Authentication Clients > Relying Parties.
- On the My Relying Parties page, click Add a Relying Party.
- Click Add for Service Provider SAML.
- On the Basic Information page, enter the name for the application in the Name field and click Next Step.
- On the Authentication page, choose SecurID manages all authentication.
- Select a Primary Authentication Method and an Access Policy as required and click Next Step.
- Provide the Service Provider details in the following format:
- ACS URL: <Zendesk ACS URL>
- Service Provider Entity ID: <Zendesk Entity ID>
See the Notes section for instructions on how to obtain the ACS URL and Entity ID.
- In the SAML Response Protection section, choose IdP signs assertion within response.
- Download the certificate by clicking Download Certificate.
- Click Show Advanced Configuration.
- Under the User Identity section, configure Identifier Type and Property. For example, Identifier Type: Email Address and Property: mail.
- Click Save and Finish.
- On the My Relying Parties page, click the Edit drop-down icon and select the Metadata option to download the metadata.
- Click Publish Changes. Your application is now enabled for SSO.
Notes
- ACS URL can be found on the SSO Configuration page Zendesk for Service under the SAML SSO URL section.
- Entity ID can be obtained by removing /access/saml/ from the ACS URL.
Configure Zendesk for Service
Perform these steps to configure Zendesk for Service.
Procedure
- Sign in to Zendesk for Service with the admin credentials.
- Navigate to Settings > Single sign on and click Configure.
- Click Create SSO configuration and select SAML.
- Provide the following details:
- Configuration name.
- SAML SSO URL: Obtain from the metadata file downloaded from RSA.
- Certificate fingerprint: See the Notes section for the instructions on how to obtain the certificate fingerprint.
- Scroll down and select the Show button when users sign in checkbox.
- Provide a name for the button and click Save.
- Under the Team member authentication and End user authentication sections, do the following:
- Select the External authentication checkbox.
- Choose Single sign on (SSO).
- Select the checkbox for the configuration that you created.
- Choose Let them choose and click Save.
Notes
To obtain certificate fingerprint:
- Install the latest version of OpenSSL for Windows.
- Open the Windows Command-line interface.
- Navigate to the OpenSSL installation directory (the default directory is C:\OpenSSL-Win32\bin).
- Run the following commands to view the certificate fingerprint/thumbprint.
openssl x509 -noout -fingerprint -sha1 -inform pem -in <Certificate.pem>
The configuration is complete.
Return to Zendesk for Service - RSA Ready Implementation Guide.
Related Articles
Microsoft Entra ID External Authentication Methods (EAM) - Relying Party Configuration Using OIDC - RSA Ready Implementati… 547Number of Views Palo Alto NGFW Global Protect - SAML Relying Party Configuration - RSA Ready Implementation Guide 116Number of Views Microsoft Entra ID - SAML Relying Party Configuration - RSA Ready Implementation Guide 87Number of Views Microsoft Office 365 - SAML Relying Party Configuration - RSA Ready Implementation Guide 252Number of Views F5 BIG-IP APM - SAML Relying Party Configuration - RSA Ready Implementation Guide 32Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process Downloading RSA Authentication Manager license files or RSA Software token seed records When configuring LDAP or LDAPS in RSA Authentication Manager with a global catalog the connection fails
Don't see what you're looking for?