> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/administration/sso-saml2.0/jumpcloud.md).

# JumpCloud

Setting up SAML2.0 SSO with JumpCloud as an IdP for Currents

{% hint style="info" %}
Once SSO is on, people with an email on your listed domains sign in through your IdP. They can't use a password or social sign-in for Currents.
{% endhint %}

### Supported Features

* SP-initiated SSO (Single Sign-On)
* Just-In-Time provisioning
* [JumpCloud User provisioning](/dashboard/administration/sso-saml2.0/jumpcloud/jumpcloud-user-provisioning.md)

### Setup Steps

{% stepper %}
{% step %}
Create a new SSO Application: **User Authentication > SSO Applications > + Add New Application.**

Type **Currents** and then click **Create a Custom Integration > Next**

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FdjNweqS2qxeKrigIDW8u%2Fcurrents-2025-04-21-11.37.28%402x.png?alt=media&amp;token=2d736b43-9229-47d0-8c06-43fec9ff045a" alt=""><figcaption><p>Creating Custom SSO Integration</p></figcaption></figure>
{% endstep %}

{% step %}
Choose Integration Options

* ✅ Select **Manage SSO** + **Configure SSO with SAML**
* ✅ **Export user to this app**
* Click **Next**, set **Integration Name,** then click **Create Application**

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FNcqgsBv3WhgCAdVPblr0%2Fcurrents-2025-04-21-11.39.57%402x.png?alt=media&amp;token=611f785d-c124-4743-a859-448b18c0b83c" alt=""><figcaption><p>Creating Custom JumpCloud SSO Integration</p></figcaption></figure>
{% endstep %}

{% step %}
Configure SSO Settings

* Fill in the fields according the values defined in [SAML2.0 Configuration](/dashboard/administration/sso-saml2.0/saml2.0-configuration.md)
  * SP Entity ID
  * ACS URL
  * SAMLSubject NameID
  * SAMLSubject NameID Format
  * Signature Algorithm: RSA-SHA256
  * Login URL: you will be able to define the login URL after Currents support team activated the integration. See [IdP-initiated Sessions](/dashboard/administration/sso-saml2.0/idp-initiated-sessions.md).
  * Attributes: `email` and `fullname`
* Click **Export Metadata,** ensure **t**he generated metadata XML has `HTTP-POST` and `HTTP-Redirect` bindings, for example:

  ```
  <md:SingleSignOnService
      Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
      Location="https://sso.jumpcloud.com/saml2/currents"
  />
  <md:SingleSignOnService
      Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
      Location="https://sso.jumpcloud.com/saml2/currents"
  />
  ```

{% endstep %}

{% step %}

#### Done

* Submit the Metadata XML file and the organization's email domains from the dashboard - see [Setting Up SSO](/dashboard/administration/sso-saml2.0/setting-up-sso.md). The values the SAML application itself needs are in [SAML2.0 Configuration](/dashboard/administration/sso-saml2.0/saml2.0-configuration.md).
* Assign users or groups to the newly created SSO application
* Set Login URL after Currents support team activated the integration. See [IdP-initiated Sessions](/dashboard/administration/sso-saml2.0/idp-initiated-sessions.md).
  {% endstep %}
  {% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/dashboard/administration/sso-saml2.0/jumpcloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.