Skip to content
Integrations/JumpCloud/Connection Guide
Connection Guide

Connect JumpCloud Without Breaking the Audit Trail

Use this guide to connect JumpCloud or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryIdentity
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect JumpCloud and make sure the first collection lands cleanly.

  1. 1
    Generate a JumpCloud API key with read access to Users and Systems.
  2. 2
    Ensure the API key can read Organizations to retrieve password policy settings.
  3. 3
    Configure api_key as a secret.
  4. 4
    Validate connection, run full sync; incremental advances a time watermark cursor.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

api_key

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.