Skip to content
Dashboard
Theme
Theme

Okta OIDC single sign-on

Set up OIDC single sign-on with Okta

View Markdown

Create an OpenID Connect app in Okta, add the redirect URI from this setup, assign your users and enter the app’s issuer and credentials here.

The values in braces, such as {redirect_uri}, 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 admin console of Okta, create a new OpenID Connect web application for this app: a confidential client that signs users in with the authorization code flow. Give it a name your users will recognize.

  2. Add {redirect_uri} to the app’s sign-in redirect URIs, exactly as shown. A redirect URI that differs by one character is refused.

    Paste into Okta:

    • Redirect URI: {redirect_uri}

    Fixes: oidc_token_exchange_failed

  3. Allow the openid, email and profile scopes, so the ID token carries the email, email_verified, given_name and family_name claims.

    Fixes: oidc_email_missing, oidc_email_not_verified

  4. To send groups, add a groups claim with the user’s group names to the ID token. Okta does not send groups unless you add this claim.

  5. Assign the people or groups who should sign in to this app with single sign-on.

  6. Copy the app’s client ID and client secret into this setup. Keep the secret only here, and enter a new one in this setup whenever you rotate it.

    Fixes: oidc_token_exchange_failed

  7. Enter the issuer URL in this setup. For Okta it has the form “https://your-okta-domain/oauth2/your-authorization-server-id”. We read the provider’s endpoints and keys from the issuer’s /.well-known/openid-configuration document.

    Fixes: oidc_discovery_unreachable, oidc_id_token_invalid

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