Skip to content
Dashboard
Theme
Theme

Okta SAML single sign-on

Set up SAML single sign-on with Okta

View Markdown

Create a SAML 2.0 app integration in Okta, paste the values from this setup, assign your users and share the app’s metadata with us.

The values in braces, such as {acs_url}, are specific to your connection. The setup link from the application you are connecting shows them with a copy button. The same steps appear there.

  1. In the Okta Admin Console, go to Applications and Resources > Applications, select Create App Integration, choose SAML 2.0 as the sign-in method and select Next. Give the app a name your users will recognize and select Next.

  2. In Single sign-on URL, paste {acs_url}. Keep “Use this for Recipient URL and Destination URL” selected.

    Paste into Okta:

    • ACS URL: {acs_url}

    Fixes: saml_destination_mismatch, saml_response_malformed

  3. In Audience URI (SP Entity ID), paste {sp_entity_id}.

    Paste into Okta:

    • SP entity ID: {sp_entity_id}

    Fixes: saml_audience_mismatch

  4. Set Name ID format to EmailAddress and Application username format to Email.

    Fixes: saml_nameid_missing

  5. Under Show Advanced Settings, keep Response and Assertion Signature set to Signed and Signature Algorithm set to RSA-SHA256.

    Fixes: saml_signature_missing, saml_signature_algorithm_weak

  6. Under Attribute Statements, add email mapped to user.email, firstName mapped to user.firstName and lastName mapped to user.lastName. To send groups, add a group attribute statement named groups.

    Fixes: saml_email_missing

  7. Select Next, choose “I’m an Okta customer adding an internal app” and select Finish.

  8. On the app’s Assignments tab, assign the people or groups who should sign in with single sign-on.

    Fixes: saml_idp_status_error

  9. On the app’s Sign On tab, copy the metadata URL (or download the metadata file) and add it to this setup. Do this again whenever the signing certificate changes.

    Fixes: saml_signature_invalid, saml_issuer_mismatch

  10. Run a test sign-in in this setup, signing in as a user you assigned to the app.

If our main network ever has an outage, sign-ins can continue through a standby address, but only if Okta accepts it. In the app’s SAML settings, under Show Advanced Settings, turn on “Other Requestable SSO URLs” and add {standby_acs_url} with index 1. Then confirm in this setup that you added it.

Paste into Okta:

  • Standby ACS URL: {standby_acs_url}

This step is optional. See standby route behavior for what the standby address does during an outage.