How DSALTA integrates with JumpCloud — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to JumpCloud using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.
Read-only access. DSALTA never modifies, creates, or deletes resources in your JumpCloud environment.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.
DSALTA reads the JumpCloud user roster — names, emails, active status, MFA status and account creation dates, which appears on your Access page. JumpCloud’s directory API has no per-user role, so the role column is left blank. It also reads the enrolled systems, which appear on your Devices page — with one limitation: JumpCloud’s /systems API reports only disk encryption (FileVault/BitLocker), so DSALTA fills in encryption status from JumpCloud while screen lock, antivirus and password manager are recorded as not present for every JumpCloud device, whatever the machine’s real configuration. Treat those three columns as unknown for JumpCloud-sourced devices.It calls these JumpCloud endpoints:
/systemusers
/systems
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your JumpCloud environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the JumpCloud card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from JumpCloud. This usually happens when API tokens expire.
Data is not syncing
Verify the connected account still holds the permissions this integration requires. Then open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Sync from integrations at the top right. That button refreshes every connected integration at once — there is no per-integration sync control.
Before you begin
A JumpCloud admin account with API key access enabled. JumpCloud disables API key access by default on newly created admin accounts, and only an Administrator with Billing can enable it for another admin.
1
Start in DSALTA
Open Integrations in the DSALTA sidebar, find JumpCloud, and click Connect to open the connect panel.
2
Create a JumpCloud API key
In the JumpCloud Admin Portal (https://console.jumpcloud.com): click your account email (top-right) → My API Key → generate and copy the key. ⚠️ The key inherits your admin permissions — keep it secret. You’ll paste it in the next step.
Generating a new key revokes the existing one — anything still using the old key stops working. JumpCloud only reveals an API key at the moment it is created, so an existing key cannot be read back. If this admin account’s key is already in use elsewhere and you no longer have a copy, either generate a new key and update those other integrations too, or create a separate admin account for DSALTA and use its key.
Set the Expiration Date before you copy the key. A newly generated JumpCloud API key defaults to a 90-day expiry; the menu offers 30, 60 or 90 days, No Expiration, or a custom value from one hour up to 365 days. JumpCloud emails the key’s owner daily starting 7 days before it expires. Admin accounts created before 15 July 2024 default to no expiration. When the key expires the JumpCloud sync stops, and because DSALTA has no Reconnect button the only repair is Disconnect and connect again — which permanently deletes the JumpCloud evidence and test results DSALTA has collected. Choose No Expiration, or diary the renewal.
A JumpCloud API key starts with the prefix jca_ — if what you copied does not begin with jca_, you have the wrong value.
A JumpCloud service account will not work here, even though it is the least-privilege option. Service accounts authenticate with an OAuth 2.0 client-credentials flow (Authorization: Bearer <access_token> obtained from https://admin-oauth.id.jumpcloud.com/oauth2/token), whereas this connection sends the credential as a JumpCloud personal admin API key. Use the My API Key value of a dedicated admin account instead.
3
Finish in DSALTA
Return to the connect panel you opened in step 1, enter the credential you just created, and confirm to complete the connection.
Once connected, JumpCloud appears on the Connected tab and the checks below begin reporting after the first sync.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)
