Zendesk for Sales - SAML Relying Party Configuration – RSA Ready Implementation Guide
Configure the RSA Cloud Authentication Service
Perform these steps to configure the RSA Cloud Authentication Service as Relying Party to Zendesk for Sales.Procedure
- Sign in to the RSA Cloud Administration Console with Administrator credentials.
- Click Authentication Clients > Relying Parties on the menu at the top of the screen.
- Click Add a Relying Party.
- In the Relying Party Catalog, click Add corresponding to 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 Access Policy as required and click Next Step.
- Enter the Service Provider details ACS URL and Service Provider Entity ID.
See the Notes section for instructions on how to obtain the ACS URL and Entity ID for Zendesk for Sales. - In the SAML Response Protection section, choose IdP signs assertion within response.
- Click Download Certificate to download the certificate.
- Choose Show Advanced Configuration and configure Identifier Type and Property under the User Identity section as shown in the example in the following screenshot.
- Click Save and Finish.
- Go to the My Relying Parties page and choose Metadata from the Edit dropdown menu to download the metadata.
- Click Publish Changes. After publishing, your application is now enabled for SSO.
Notes
To obtain the ACS URL and Service Provider Entity ID for Zendesk, perform the following:On Zendesk for Sales, go to the SSO Configuration page. The ACS URL is under the SAML SSO URL section.
To obtain the Service Provider Entity ID, remove “/access/saml/” from the ACS URL.
Configure Zendesk for Sales
Perform these steps to configure Zendesk for Sales.Procedure
- Login to Zendesk for Sales with Administrator credentials.
- Navigate to Settings > Single Sign on and click Configure.
- Click Create SSO configuration, then select SAML.
- Provide the following details:
Configuration name: Name for your identity provider configuration.
SAML SSO URL: The value of SingleSignOnService, which can be found in the metadata file downloaded from RSA.
Certificate fingerprint: Refer to the note below for instructions on how to obtain the certificate fingerprint. - Scroll down and select Show button when users sign in, then provide a name for the button, and click Save.
- Under the Team member authentication section, do the following:
Select External authentication.
Select Single sign on (SSO).
Repeat the same steps for the End user authentication section. - The Configuration name you chose in Step 4 will appear. Select the configuration name and select Let them choose, then click Save.
Notes
To obtain certificate fingerprint, perform the following:- Install the latest version of OpenSSL for Windows.
- Open the Windows Command Line.
- Navigate to the OpenSSL installation directory (the default directory is C:\OpenSSL-Win32\bin).
- Run the following commands to view the certificate fingerprint/thumbprint.
Certificate.pem is the file downloaded from RSA.
The configuration is complete.
Return to Zendesk for Sales - RSA Ready Implementation Guide.
Related Articles
Zendesk for Sales - RSA Ready Implementation Guide 7Number of Views Information about the RSA SecurID Access Cloud Authentication Service license 212Number of Views RSA October 2025 Release Announcements 20Number of Views OAuth 2.0-Based Permissions for the Cloud Administration APIs 68Number of Views How to fix Account Collector for Active Directory when it fails with java.lang.NoClassDefFoundError in RSA Via Lifcycle an… 206Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?