Skip to main content
Connect JumpCloud to Oleria to gain continuous visibility into who has access across your directory. Oleria reads identity and access data from the JumpCloud Directory Platform API - mapping every user, their group memberships, and the admin roles defined in your tenant - so you can see where access is over-provisioned and take action directly from Oleria. This page provides step-by-step guidance for connecting JumpCloud to Oleria.

​
What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your JumpCloud directory:
  • Accounts - every directory (system) user in your JumpCloud tenant.
  • User groups - all user groups and their membership, including whether a group is dynamic (membership set by a query) or static (membership set manually).
  • Admin roles - the admin-portal roles defined in your tenant.
JumpCloud does not expose an API to list which accounts hold which admin role. Oleria discovers the role definitions in your tenant, but cannot map which users are assigned to them. See Known limitations.

​
Prerequisites

  • A JumpCloud administrator account
  • API access enabled for that admin account (see the next section)
Use a service account rather than a personal employee account for the integration to ensure continuity if the employee leaves or changes roles.
Oleria connects to the JumpCloud US data center (https://console.jumpcloud.com) only. Tenants provisioned on JumpCloud’s EU or India data centers cannot be connected today.

​
Connect JumpCloud to Oleria

1

Enable API access for your admin account

Log in to JumpCloud as an administrator and go to Settings -> Administrators. Select your admin account and enable API access.
2

Copy your API key

Select your account menu in the top right of the JumpCloud console, then select My API Key. Copy the key shown.
Treat this key like a password - it authenticates as your admin account with whatever permissions that account holds. See Remediation actions for how the admin account’s role affects what Oleria can do.
3

Connect in Oleria

Go to your Oleria workspace, select Integrations -> select JumpCloud. Select Continue and fill in the connection form:Select Authenticate to validate and save the integration. Oleria checks the credentials against JumpCloud before saving.

​
Verify the integration

Confirm the JumpCloud instance appears in your Oleria workspace connected integrations. After the first sync completes, you can review the discovered accounts, groups, and roles in your Oleria workspace.
If you rotate the API key, update the credentials in Oleria by editing the integration. A revoked or expired key will cause discovery to stop.

​
Remediation actions

Beyond discovery, Oleria can act on JumpCloud access to remediate risk.
Reactivating a suspended account isn’t a standalone action you select in Oleria - it’s only available as the automatic revert of a prior Suspend user account action.
JumpCloud has no API to check in advance whether an admin account can perform these actions. An API key created under a Read Only Administrator account connects successfully and passes validation, but any remediation action will fail when it runs. Use a Full Administrator (or another role with write access to users and user groups) to create the API key if you plan to use remediation actions.

​
Known limitations

  • Admin role assignments are not mapped - JumpCloud’s API has no endpoint to list which accounts hold which admin-portal role. Oleria discovers the role definitions that exist in your tenant, but cannot show which users are assigned to them.
  • Scope is Users, Groups, and Roles only - this integration does not cover JumpCloud’s device/MDM management, RADIUS/LDAP, SSO application entitlements, or its separate directory activity/audit log.
  • US data center only - tenants on JumpCloud’s EU or India data centers cannot be connected by this integration today.
  • Multi-organization (MSP) accounts - if your API key has access to more than one JumpCloud organization, Oleria connects to and syncs only the first organization returned by JumpCloud. Other organizations under the same MSP account are not synced.

​
Contact us

For questions about this integration, contact us at support@oleria.com.