Skip to main content

JumpCloud

Visualize JumpCloud users, groups, and applications, map JumpCloud users to employees, and monitor changes through queries and alerts.

Installation​

info

JupiterOne requires a Read Only Admin API key used to authenticate with the JumpCloud account.

Each JupiterOne integration instance ingests a single JumpCloud organization. If your API key is a multi-tenant (MTP) admin key that can see more than one organization, you must also provide an Organization ID, and you need one integration instance per organization.

warning

JumpCloud Service Account keys are not supported. This integration uses an administrator API key; create one as described below rather than a Service Account key.

Configuration in JumpCloud​

note

API access is disabled for administrators by default, and only an administrator with the Administrator with Billing role can enable it. If you cannot enable API access on the account below, ask such an administrator to turn it on for you.

  1. Log in to the JumpCloud Admin Portal.
  2. Create a new administrator with the Read Only role:
    • Go to Settings > Administrators.
    • Click Add Administrator, then Create New Admin.
    • Enter the required fields.
    • Set the role to Read Only.
    • Select Enable API access.
    • Click Save.
  3. Log in to the Admin Portal as the new Read Only administrator.
  4. In the bottom left, click your account name and select My API Key.
  5. If no key exists yet, click Generate New API Key. Copy the key (it begins with jca_ and is shown only once) for use in the next section.

Finding your Organization ID​

Only required if your API key is a multi-tenant (MTP) admin key that can see more than one JumpCloud organization. Single-tenant admin keys can skip this section.

  1. Log in to the JumpCloud Admin Portal.
  2. Select the organization you want this integration instance to ingest.
  3. Go to Settings > Organization Profile > General.
  4. Next to Organization ID, click the eye icon to display all characters, then click the copy icon to copy the ID for use in the next section.

Repeat for each organization you want to ingest. Each one needs its own JupiterOne integration instance.

Configuration in JupiterOne​

To install the JumpCloud integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select JumpCloud. Click New Instance to begin configuring your integration, providing the following:

  • Account Name used to identify the JumpCloud account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName option is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • API Key from an Admin with the Read Only role.

  • Organization ID of the single JumpCloud organization this instance ingests. Required if your API key is a multi-tenant (MTP) admin key that can see more than one organization; the integration cannot start without it in that case. Leave blank for single-tenant admin keys, where the organization is resolved automatically.

Click Create once all values are provided to finalize the integration.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.