# JumpCloud

{% hint style="info" %}
Enabling SSO will affect all users of your organization, users would not be able to sign in to Currents using a different authorization method when SSO is enabled.
{% 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="/files/l74ZL7YQkgwa6puOePVm" 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="/files/0RvjMTZxLYhO8gA99Q4a" 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

* Share the Metadata XML file together with other details appearing in [SAML2.0 Configuration](/dashboard/administration/sso-saml2.0/saml2.0-configuration.md) with Currents support team to active the SSO.
* 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: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.