# JumpCloud SAML single sign-on

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

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.

:::caution[Verification]
Not yet verified on a real JumpCloud tenant. It was written from the public JumpCloud documentation, so labels in the admin console may differ slightly.
:::

The values in braces, such as `{sp_entity_id}`, 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.

## Steps

<ol class="idp-steps">

<li class="idp-step">

<a id="create-app"></a>

### Add a custom SAML application

In the JumpCloud Admin Portal, open SSO Applications, add a new application, choose a custom SAML application and give it a display name.

:::caution[Labels not confirmed in step 1]
The JumpCloud support page refused automated reads on 2026-10-11 (HTTP 403); every label in this guide is written generically.
:::

</li>

<li class="idp-step">

<a id="entity-ids"></a>

### Enter the entity IDs

On the SSO tab, enter an IdP entity ID that is unique to this app, and paste `{sp_entity_id}` into SP Entity ID.

<div class="setup-values">

Paste into JumpCloud:

- SP entity ID: `{sp_entity_id}`

</div>

Fixes: [`saml_audience_mismatch`](/errors/saml_audience_mismatch/), [`saml_issuer_mismatch`](/errors/saml_issuer_mismatch/)

:::caution[Labels not confirmed in step 2]
Field labels not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="acs"></a>

### Enter the ACS URL

Paste `{acs_url}` into the ACS URL field.

<div class="setup-values">

Paste into JumpCloud:

- ACS URL: `{acs_url}`

</div>

Fixes: [`saml_destination_mismatch`](/errors/saml_destination_mismatch/), [`saml_response_malformed`](/errors/saml_response_malformed/)

:::caution[Labels not confirmed in step 3]
Field label not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="name-id"></a>

### Send the email address as the name ID

Set the SAML subject name ID to the user's email and its format to email address.

Fixes: [`saml_nameid_missing`](/errors/saml_nameid_missing/)

:::caution[Labels not confirmed in step 4]
Field label not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="signing"></a>

### Check the signing settings

Sign the assertion (or the response) and set the signature algorithm to RSA-SHA256.

Fixes: [`saml_signature_missing`](/errors/saml_signature_missing/), [`saml_signature_algorithm_weak`](/errors/saml_signature_algorithm_weak/)

:::caution[Labels not confirmed in step 5]
Field labels not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="attributes"></a>

### Add the attributes

Add user attributes named email, firstName and lastName mapped to the user's email, first name and last name.

Fixes: [`saml_email_missing`](/errors/saml_email_missing/)

:::caution[Labels not confirmed in step 6]
Field labels not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="assign"></a>

### Bind your user groups

On the app's user groups tab, bind the groups whose members should sign in with single sign-on, then activate or save the app.

Fixes: [`saml_idp_status_error`](/errors/saml_idp_status_error/)

:::caution[Labels not confirmed in step 7]
Field labels not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="metadata"></a>

### Share the identity provider metadata

Export the app's metadata (or download its IdP certificate) and add it to this setup. Do this again whenever the certificate changes.

Fixes: [`saml_signature_invalid`](/errors/saml_signature_invalid/)

:::caution[Labels not confirmed in step 8]
Field labels not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="test"></a>

### Test the connection

Run a test sign-in in this setup, signing in as a member of a bound group.

</li>

</ol>

<a id="standby"></a>

## Optional: add the standby ACS URL

If our main network ever has an outage, sign-ins can continue through a standby address, but only if JumpCloud accepts it. If the app lets you add more than one ACS URL, add `{standby_acs_url}` as the second one and keep `{acs_url}` as the default. If it allows only one, skip this step. Then confirm in this setup that you added it.

<div class="setup-values">

Paste into JumpCloud:

- Standby ACS URL: `{standby_acs_url}`
- ACS URL: `{acs_url}`

</div>

This step is optional. See [standby route behavior](/trust/standby/) for what the standby address does during an outage.

## Sources

- [Single sign-on (SSO) with SAML 2.0 (JumpCloud Support)](https://jumpcloud.com/support/sso-with-saml-2-0), read on 2026-10-11
