Description
The JumpCloud connector uses the JumpCloud Directory Insights and Core API over HTTPS to discover user identities, user groups, and system associations within a JumpCloud organisation. It authenticates using an API key and provides visibility into cloud-native directory access across device and application integrations.
System Type Classification
| Field | Value |
|---|
| System Type | Directory Service |
| Default Scan Priority | 10 |
Version Support
| OrbisID Edition | Supported |
|---|
| Community | No |
| Pro | Yes |
| Enterprise | Yes |
Supported Protocol
| Protocol | Port | Notes |
|---|
| REST API (HTTPS) | 443 TCP | API key via x-api-key request header |
What OrbisID Discovers
| Data | Source |
|---|
| User accounts | GET /api/v2/users |
| User groups | GET /api/v2/usergroups |
| Group memberships | GET /api/v2/usergroups/{id}/members |
| User enabled state | activated and suspended flags |
| Admin / MFA status | admin flag and mfa object per user |
NHI Subtype Classification
This connector does not yet assert an NHI (Non-Human Identity) subtype directly from JumpCloud's API — accounts are classified via the naming-pattern catalogue rules and AI classifier (Tier B) only. JumpCloud's Applications/SSO API (/api/v2/applications) and edition-dependent API-key-bound system users are the likely real signal for a future connector-asserted classification, but the exact response shape was not confirmed against a live tenant, so it was not implemented here.
Connection Requirements
Required Permissions
Generate a JumpCloud API key with read access from an admin account.
Minimum permissions:
- JumpCloud Administrator or Manager role (API key scope inherits the account's role)
Credential Mapping
| OrbisID Field | Value |
|---|
credential.password | JumpCloud API key |
system.hostname | console.jumpcloud.com (or custom tenant URL) |
Network Requirements
The OrbisID server must have HTTPS access to console.jumpcloud.com on port 443.
Configuration Steps
- In the JumpCloud admin portal, navigate to Administrator Account → API Settings → Generate New API Key
- Copy the API key (displayed only once)
- Create a Credential in OrbisID:
- Password: JumpCloud API key
- Navigate to Systems → Add System
- Fill in the fields:
| Field | Value |
|---|
| Name | Descriptive name (e.g., JumpCloud – Corp Directory) |
| OS Type | JumpCloud |
| System Type | Directory Service |
| Hostname | console.jumpcloud.com |
| Credential | The API key credential |
- Click Test Connection
- Click Save
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|
401 Unauthorized | Invalid API key | Regenerate the API key in the JumpCloud portal |
| No users returned | Organisation empty or key lacks scope | Verify users exist and the API key belongs to an Administrator |
| Rate limit errors | Too many API calls | OrbisID applies back-off automatically; increase the scan interval |
| Cannot connect | Outbound HTTPS blocked | Ensure the OrbisID server can reach console.jumpcloud.com:443 |