ConductorOne provides identity governance for JumpCloud. Integrate your JumpCloud instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of JumpCloud credentials generated by following the instructions above
Cloud-hosted
Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
1
In ConductorOne, navigate to Admin > Connectors and click Add connector.
2
Search for JumpCloud and click Add.
3
Choose how to set up the new JumpCloud connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Paste the API key into the API key field.
8
Click Save.
9
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your JumpCloud connector is now pulling access data into ConductorOne.
Follow these instructions to use the JumpCloud connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
In ConductorOne, navigate to Connectors > Add connector.
2
Search for Baton and click Add.
3
Choose how to set up the new JumpCloud connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
In the Settings area of the page, click Edit.
7
Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
2
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the JumpCloud connector to. JumpCloud data should be found on the Entitlements and Accounts tabs.
That’s it! Your JumpCloud connector is now pulling access data into ConductorOne.
If JumpCloud is your company’s identity provider (meaning that it is used to SSO into other software), the connector sync will automatically create applications in ConductorOne for all of your SCIMed software. Before you move on, review the Create applications page for important information about how to set up connectors for the SCIMed apps.
Why do I see multiple accounts for some JumpCloud users?
JumpCloud separates users and admin users, giving each a separate identity and login. Because of this, a user who is both a user and an admin user in JumpCloud will have two JumpCloud accounts in ConductorOne.
Why don’t I see profile attributes listed for a JumpCloud admin user?
An admin user in JumpCloud is intended only to manage the JumpCloud tenant, and not to be an identity that gains access to resources. Because of this design, admin users are not associated with the profile attributes, such as department or job title, that are associated with a non-admin user account.
