# OneLogin

<!-- Generated by scripts/generate.ts. Do not edit. -->

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

- [Set up SCIM directory sync with OneLogin](/idp-guides/onelogin/directory-sync/): Add the OneLogin SCIM provisioner app, connect it with the URL and token from this setup, turn on provisioning and give your users access.
- [Set up SAML single sign-on with OneLogin](/idp-guides/onelogin/sso/): Add a SAML app in OneLogin, paste the values from this setup, give your users access and share the app's metadata with us.

## Connection Doctor fixes

Connection Doctor shows these steps when a test or sign-in through OneLogin fails. Codes without their own OneLogin steps use the [generic fixes](/idp-guides/generic/). Values in braces are filled in with the connection's own settings in the dashboard and portal.

<a id="oidc_email_missing"></a>

### Fix for `oidc_email_missing`

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](/errors/oidc_email_missing/).

<a id="oidc_idp_error"></a>

### Fix for `oidc_idp_error`

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](/errors/oidc_idp_error/).

<a id="oidc_token_exchange_failed"></a>

### Fix for `oidc_token_exchange_failed`

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](/errors/oidc_token_exchange_failed/).

<a id="saml_audience_mismatch"></a>

### Fix for `saml_audience_mismatch`

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](/errors/saml_audience_mismatch/).

<a id="saml_destination_mismatch"></a>

### Fix for `saml_destination_mismatch`

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](/errors/saml_destination_mismatch/).

<a id="saml_email_missing"></a>

### Fix for `saml_email_missing`

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](/errors/saml_email_missing/).

<a id="saml_idp_status_error"></a>

### Fix for `saml_idp_status_error`

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](/errors/saml_idp_status_error/).

<a id="saml_issuer_mismatch"></a>

### Fix for `saml_issuer_mismatch`

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](/errors/saml_issuer_mismatch/).

<a id="saml_nameid_missing"></a>

### Fix for `saml_nameid_missing`

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](/errors/saml_nameid_missing/).

<a id="saml_signature_algorithm_weak"></a>

### Fix for `saml_signature_algorithm_weak`

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](/errors/saml_signature_algorithm_weak/).

<a id="saml_signature_invalid"></a>

### Fix for `saml_signature_invalid`

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](/errors/saml_signature_invalid/).

<a id="saml_signature_missing"></a>

### Fix for `saml_signature_missing`

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](/errors/saml_signature_missing/).
