Okta

How to Configure SAML 2.0 for Simpplr

  1. Log in to Simpplr as an administrator and click Go To Salesforce.

  2. Navigate to Setup > Security Controls > Single Sign-On Settings, then click Edit:

    “simpplr1.png"

  3. Under Single Sign-On Settings, check the SAML Enabled box:

    “simpplr2.png"

  4. Click New:

    “simpplr3.png"

  5. Enter the following (see screen shot at end of step for reference):

    • Issuer: Copy and paste the following:

      Sign into the Okta Admin Dashboard to generate this variable.

    • Identity Provider Certificate:

      • Copy and save the following:

        Sign into the Okta Admin Dashboard to generate this variable.

      • Click Browse and select the certificate you just saved to upload:

    • Signing Certificate: Select Default Certificate.

    • Assertion Decryption Certificate: Select Assertion not encrypted.

    • SAML Identity Type: Check Assertion contains User's salesforce.com username.

    • SAML Identity Location: Check Identity is in the NameIdentifier element of the Subject statement.

    • Identity Provider Login URL: Copy and paste the following:

      Sign into the Okta Admin Dashboard to generate this variable.

    • Identity Provider Logout URL: Copy and paste the following:

      Sign into the Okta Admin Dashboard to generate this variable.

    • Service Provider Initiated Request Binding: Check HTTP POST.

    • Click Save.

    “simpplr4.png"

  6. Make a copy of the Salesforce Login URL and Entity ID:

    “simpplr5.png"

  7. In Okta, select the General tab for the Simpler app, then copy the values for Salesforce Login URL and Entity ID that you copied into the SSO URL and Audience Restriction fields, then click Save.

    “simpplr6.png"

  8. Navigate to Setup > Domain Management > Domains, and select your domain:

    “simpplr7.png"

  9. Scroll to the Login Page Settings section and click Edit:

    “simpplr9.png"

  10. Check the Okta box, then click Save:

    “simpplr10.png"

  11. Done!

    Notes:

    IdP-initiated flows and SP-initiated flows are supported.

    Just In Time (JIT) provisioning is not supported.