Information to be shared from Sprinklr to customer for SSO

Updated 

Before configuring SSO on the Sprinklr platform, there are some steps that need to be performed on the Identity Provider side for beginning the process. The steps to obtain the information needed to be shared with the client from Sprinklr for setting up SSO details on the IDP end are mentioned in this article below.

Information to be Shared from Sprinklr

  • Service provider (Sprinklr in this case) details including:

    • Service Provider Login URL: https://{prefix-of-domain}.sprinklr.com.   

      The naming convention is https://x.sprinklr.com for the production and https://staging-x.sprinklr.com for staging (testing process), where x is the name of Client. e.g., https://wellsfargo.sprinklr.com and https://staging-wellsfargo.sprinklr.com

      Note that the domain needs to be set by the ITOPs.

    • Entity ID from Sprinklr: Usually it is https://saml.sprinklr.com for all environments, including app, prod0, and prod2. Note: You cannot use the same Entity ID twice for a client who wants two SSO configurations in the same environment as it is a unique identifier in the environment’s SSO configurations.

    • ACS URL : https://{prefix-of-domain}.sprinklr.com/ui/sso/saml/{partnerId}

      • The naming convention is https://x.sprinklr.com/ui/sso/saml/{partnerId} for the production and https://staging-x.sprinklr.com/ui/sso/saml/{partnerId} for the staging, where x is the name of the Client. The staging URL should be the custom domain that we can fetch from the backend for any partner.

      • At the end of the ACS URL you will need to enter the partner ID highlighted in red.

  • Public Key Certificate of Sprinklr for SAML. (Certificate Download Link) : https://www.google.com/url?q=https://sprinklr.atlassian.net/wiki/download/attachments/6193306/ssonew.pem?version%3D1%26modificationDate%3D1400568707000%26cacheVersion%3D1%26api%3Dv2&sa=D&source=docs&ust=1671526424742999&usg=AOvVaw0vcawTTd46ZKETfdoRQFwI.

    Note: The above certificate is for staging in the prod0 (partner ID: 9056). This certificate is also mentioned in this mapping sheet.