# JumpCloud

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

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

- [Set up SCIM directory sync with JumpCloud](/idp-guides/jumpcloud/directory-sync/): Turn on identity management with SCIM for your JumpCloud application, connect it with the URL and token from this setup and bind the groups to sync.
- [Set up SAML single sign-on with JumpCloud](/idp-guides/jumpcloud/sso/): Add a custom SAML application in JumpCloud, paste the values from this setup, bind your user groups and share the app's metadata with us.

## Connection Doctor fixes

Connection Doctor shows these steps when a test or sign-in through JumpCloud fails. Codes without their own JumpCloud 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 JumpCloud, open the OIDC application and add the email scope/attribute.

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 JumpCloud, open SSO Applications > the OIDC application > User Groups and bind a group that contains the user, 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 JumpCloud, open the OIDC application and add `{redirect_uri}` to Redirect URIs; regenerate the client secret if needed.

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 JumpCloud, open the SSO application and set SP Entity ID 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 JumpCloud, open the SSO application and set ACS URLs 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 JumpCloud, open the SSO application > Attributes and add Service Provider Attribute Name email mapped to JumpCloud Attribute email.

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 the JumpCloud Admin Portal, open the SSO application > User Groups and bind the user's group.

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 JumpCloud, check the SSO application's IdP Entity ID and upload its exported 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 JumpCloud, open the SSO application and set SAMLSubject NameID (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 JumpCloud, open the SSO application and set Signature Algorithm to RSA-SHA256.

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 JumpCloud, open the SSO application > IDP Certificate and download it (or Export Metadata), then 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 JumpCloud, open the SSO application and enable Sign Assertion (or Sign Response).

See the [`saml_signature_missing` error reference](/errors/saml_signature_missing/).
