Skip to content
Dashboard
Theme
Theme

OneLogin

Setup guides for OneLogin.

View Markdown

Setup guides for OneLogin. IT administrators see the same steps, with their own values filled in, in the setup link they receive.

Connection Doctor shows these steps when a test or sign-in through OneLogin fails. Codes without their own OneLogin steps use the generic fixes. Values in braces are filled in with the connection’s own settings in the dashboard and portal.

The identity provider did not release the user’s email claim.

  1. In OneLogin, open the OIDC app > SSO and make sure the email scope is allowed.

See the oidc_email_missing error reference.

The identity provider returned an error to the sign-in callback instead of signing the user in (most often the user is not assigned to the application, or canceled).

  1. In OneLogin, open Applications > the OIDC app > Users (or the user’s Applications tab) and give the user access to the app, then retry.

See the oidc_idp_error error reference.

The identity provider refused to exchange the sign-in code (often a wrong client secret or redirect URI).

  1. In OneLogin, open the OIDC app > Configuration and add {redirect_uri} to Redirect URIs; check the client secret under SSO.

See the oidc_token_exchange_failed error reference.

The identity provider uses a different SP Entity ID (Audience) than this connection’s.

  1. In OneLogin, open the app > Configuration and set Audience (EntityID) to {sp_entity_id}.

See the saml_audience_mismatch error reference.

The identity provider sends the response to a different address than this connection’s.

  1. In OneLogin, open the app > Configuration and set ACS (Consumer) URL and Recipient to {acs_url}.

See the saml_destination_mismatch error reference.

The response does not include the user’s email address.

  1. In OneLogin, open the app > Parameters, add a parameter named email mapped to Email and include it in the SAML assertion.

See the saml_email_missing error reference.

The identity provider refused the sign-in before sending an assertion.

  1. In OneLogin, open Applications > the app > Users (or assign the app to the user’s role).

See the saml_idp_status_error error reference.

The response comes from a different identity provider (issuer) than the one configured here.

  1. In OneLogin, open the app > SSO and copy the Issuer URL, or upload the app’s SAML metadata here.

See the saml_issuer_mismatch error reference.

The response has no user identifier (NameID).

  1. In OneLogin, open the app > Configuration/Parameters and set the NameID value (for example Email).

See the saml_nameid_missing error reference.

The response is signed with SHA-1, which is not accepted.

  1. In OneLogin, open the app > SSO and set SAML Signature Algorithm to SHA-256.

See the saml_signature_algorithm_weak error reference.

The signature does not match the identity provider certificate we have on file (often after a certificate change).

  1. In OneLogin, open the app > SSO > X.509 Certificate > View Details, download it and upload it here.

See the saml_signature_invalid error reference.

The SAML response or assertion is not signed.

  1. In OneLogin, open the app > SSO and set SAML Signature Element to Assertion or Both.

See the saml_signature_missing error reference.