Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather JumpCloud credentials

Each setup method requires you to pass in credentials generated in JumpCloud. Gather these credentials before you move on.

A user with an Administrator identity in JumpCloud on the relevant JumpCloud org must perform this task.

Retrieve a JumpCloud API key

1. In JumpCloud, log in as an Administrator.

2. Click your user avatar at the top right corner of the page and click My API Key.

3. Copy the API key.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a JumpCloud cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of JumpCloud credentials generated by following the instructions above

1. In ConductorOne, click Connectors > 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.

Set up a JumpCloud cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between JumpCloud and ConductorOne.

See the ConductorOne JumpCloud integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a JumpCloud self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of JumpCloud credentials generated by following the instructions above

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the JumpCloud connector

1. 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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your JumpCloud connector deployment:

Secrets configuration

# baton-jumpcloud-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-jumpcloud-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # JumpCloud credentials
  BATON_API_KEY: <JumpCloud API key>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-jumpcloud.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-jumpcloud
  labels:
    app: baton-jumpcloud
spec:
  selector:
    matchLabels:
      app: baton-jumpcloud
  template:
    metadata:
      labels:
        app: baton-jumpcloud
        baton: true
        baton-app: jumpcloud
    spec:
      containers:
      - name: baton-jumpcloud
        image: ghcr.io/conductorone/baton-jumpcloud:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-jumpcloud-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-jumpcloud
   

2. Apply the secret configuration:

   kubectl -n baton-jumpcloud apply -f baton-jumpcloud-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-jumpcloud apply -f baton-jumpcloud.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-jumpcloud}
   

3. 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.

What’s next?

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.

Troubleshooting the JumpCloud integration

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.