# JumpCloud Configuration

{% hint style="info" %}
For a 100% cloud-based integration with JumpCloud, see [Keeper SSO Connect Cloud](https://docs.keeper.io/sso-connect-cloud/)
{% endhint %}

### JumpCloud

JumpCloud instructions for setting up Single Sign On (SSO) with Keeper Security.\
\
As listed in the JumpCloud SSO Prerequisites a public certificate and a private key pair are required. Instructions can be found here:

<https://jumpcloud.com/configure/keeper-and-sso-configuration/>

Log into the JumpCloud Administrator console.

Select the **Applications** tab on the side menu.

<div align="left"><img src="/files/-LU6Uv3k1hksfsK-zt1B" alt=""></div>

Next, select the **+** icon in the upper left corner.

<div align="left"><img src="/files/-LU6VSMdHWDiv-N3HIxv" alt=""></div>

Search for **Keeper** in the Application list search bar. Select Configure on the Keeper Application.

<div align="left"><img src="/files/-LlEUUp6VnzrKofAldLj" alt=""></div>

Next, on Keeper Application connector page, enter the IDP ENTITY ID:

<div align="left"><img src="/files/-LU6X8DnOIe0MoicUNEE" alt=""></div>

The IDP ENTITY ID is a unique, case-sensitive identifier used by JumpCloud for this Service Provider (SP). This value should match the value specified in the **Entity ID** field of the Keeper SSO Connect. Your domain name, SSO Connect server name or IP address are possible examples.\
\
Next, Upload the IdP Private Key (private.pem file) and IDP Certificate (cert.pem file).

<div align="left"><img src="/files/-LU6XIFCDiMY4HLBKD0r" alt=""></div>

In the SP Entity ID field, enter the value found in the Entity ID field of the Service Provider Section from Keeper SSO Connect.

<div align="left"><img src="/files/-LU6XOTWiLN94o8JBcey" alt=""></div>

In the ACS URL field, enter the value found in the ACS URL field of the Service Provider Section from Keeper SSO Connect.

<div align="left"><img src="/files/-LU6XVn6sl30JdSWAauh" alt=""></div>

In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector. (i.e. keepersecurity)

<div align="left"><img src="/files/-LU6X_sJKar_Ut1JFJ5Z" alt=""></div>

In the Display Label field, enter a label that will appear under the Service Provider logo within the JumpCloud User console. (i.e. Keeper Security)

<div align="left"><img src="/files/-LU6XfwQEI4ucHrqufso" alt=""></div>

**Note: Keeper SSO Connect expects that the SAML response is signed.  Ensure that JumpCloud is configured to sign SAML responses.**

To complete the configuration, select the **activate** button.

<div align="left"><img src="/files/-LU6XnANjTWVCEgUaycx" alt=""></div>

Last step is to export the metadata from this connector to import it into the Keeper SSO Connect in Step 8.

![](/files/-LlEUoPcII1lfY8QA4Y0)

Upload this file into the Keeper SSO Connect interface by dragging and dropping the file into the Setup screen:

![](/files/-MYNKhnT5QWdx0WDBAmk)

Select **Save** and Your Keeper SSO Connect setup is now complete!

{% hint style="info" %}

### User Provisioning SSO+SCIM

JumpCloud® supports Automated Provisioning with SCIM (System for Cross Domain Identity Management) which will update and deactivate Keeper user accounts as changes are made in JumpCloud®.  Step-by-Step instructions can be found [here](/enterprise-guide/user-and-team-provisioning/jumpcloud-provisioning-with-scim.md)
{% endhint %}


---

# 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.keeper.io/sso-connect-on-prem/identity-provider-setup/jumpcloud-configuration.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.