# JumpCloud

Firstly, we need to obtain credentials such as

* `Client ID`
* `Client secret`

If you already have them, please skip to [#configuring-jumpcloud-as-external-oidc-in-defguard](#configuring-jumpcloud-as-external-oidc-in-defguard "mention")

## Obtaining basic credentials

1. Login to your JumpCloud admin account
2. Navigate to SSO Applications

   <figure><img src="/files/eCp9HFr0O1oXxkYTy9yq" alt=""><figcaption></figcaption></figure>
3. Add a new SSO Application
4. Select "Custom" on this screen

   <figure><img src="/files/L5kgm495VmxWwN7LhWvJ" alt=""><figcaption></figcaption></figure>
5. Select "Configure SSO with OIDC"

   <figure><img src="/files/YhhUoFI4XZlEIVTAiozz" alt=""><figcaption></figcaption></figure>
6. Fill the app's display label in the next form

   <figure><img src="/files/LypqNUT2YUwYx8eCqJQV" alt=""><figcaption></figcaption></figure>
7. After finishing this configuration, you will be redirected to your newly created SSO Application's settings. Go to the "SSO" tab first

   <figure><img src="/files/wBUbJ3bNIGVKbz8QKcxf" alt=""><figcaption></figcaption></figure>
8. Configure as following:

   <figure><img src="/files/cjrVYl7zeJ7XzmDKNl3E" alt=""><figcaption></figcaption></figure>

   Make sure to set the correct Redirect URI and Login URL that will reflect your Defguard's setup.\
   If you access your Defguard dashboard at e.g., `https://defguard.example.net` your redirect URI will be `https://defguard.example.net/auth/callback` and the login URL `https://defguard.example.net/auth/login`.\
   Additionally, if you are using a Defguard proxy to enroll users, you can also add another redirect URI in the form of `<DEFGUARD_PUBLIC_URL>/openid/callback` and `<DEFGUARD_PUBLIC_URL>/openid/mfa/callback` if you wish to use the [External MFA feature](/features/wireguard/multi-factor-authentication-mfa-2fa.md#external-mfa) (`<DEFGUARD_PUBLIC_URL>` is the address at which your Proxy enrollment page is accessible).
9. Next, select the profile scope and add an `email` user attribute mapping by hand, like so:

   <figure><img src="/files/z3xFHkxgABI8kG6K6CXK" alt=""><figcaption></figcaption></figure>

   It's important **not** to select the email standard scope checkbox, as it will automatically add a constant `email_verified` field which doesn't conform to the OpenID standard and doesn't work with Defguard.\
   You can see the following section for more information: [External SSO/OpenID providers](/features/external-openid-providers.md#jumpcloud).
10. Click "**Activate**". You will be presented with a client ID and a secret. Copy both of them, as you will need to insert them in Defguard's settings.

## Obtaining Directory synchronization credentials

{% hint style="warning" %}
JumpCloud API keys are bound to users and don't support granular permissions nor generating more than one at a time, we recommend generating the API key for a user with read only permissions, as Defguard doesn't require write permissions to your directory.
{% endhint %}

* Login to your [JumpCloud admin portal](https://console.jumpcloud.com/)
* Generate a new API key (or use an existing one). This can be done by clicking your user icon in the upper right corner and selecting "My API key"

  <figure><img src="/files/Y8e8JNG5nwVfjZgdIqjR" alt=""><figcaption></figcaption></figure>
* If you already generated an API key, you will have to regenerate it here (please note that regenerating the API key may break your existing integrations that already use it).

  <figure><img src="/files/WXtJt6H6yhuExnv5xMZP" alt=""><figcaption></figcaption></figure>

The JumpCloud directory synchronization should now work and your users' state and group memberships should be periodically synchronized

## Configuring JumpCloud as external OIDC in Defguard

1. Go to **Settings → External identity providers**

<figure><img src="/files/6b7ImsaJoEZtichzWvel" alt=""><figcaption></figcaption></figure>

2. Click "**Connect**" in row with **JumpCloud**

<figure><img src="/files/EpwxPDbEMlG0vbuu3u0J" alt=""><figcaption></figcaption></figure>

3. Fill out **Client ID** and **Client secret** (Check [#obtaining-basic-credentials](#obtaining-basic-credentials "mention"))

<figure><img src="/files/jnyVTeR7Myqzfv5VqTZE" alt=""><figcaption></figcaption></figure>

4. Click **Continue**
5. If you decide to use **Directory Synchronization**, enter **JumpCloud API Key**\
   (Check [#obtaining-directory-synchronization-credentials](#obtaining-directory-synchronization-credentials "mention"))

<figure><img src="/files/ocTAFSXFB7r6oSnU54sY" alt=""><figcaption></figcaption></figure>

6. Confirm with "**Continue**" button

<figure><img src="/files/LSzpvcxHX0oXvupUA207" alt=""><figcaption></figcaption></figure>

If no errors occurred during configuration, you will see a message indicating that your OIDC provider has been successfully added

7. Click "**Finish**" button

### Verifying setup

Back in JumpCloud, make sure your users have access to the SSO Application. You can enable it by navigating to the `User groups` menu and selecting the group you want to enable logging in through JumpCloud for. Only users from this group will be able to log in to Defguard with JumpCloud. In this example, we will select the `All users` group, which is a dynamic group containing every user.

Now in the group settings menu, select the `Applications` tab and select the checkbox next to your newly created app, this will enable the app for that group. Click `Save group` when you finish.

<figure><img src="/files/rQ01mxqY7iYQTyoSL4hV" alt=""><figcaption></figcaption></figure>

Now you should be able to log in to Defguard with JumpCloud.


---

# 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.defguard.net/features/external-openid-providers/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.