Skip to main content
OAuth 2.0 client credentials flow using a JumpCloud service account. Provides token-based authentication with automatic refresh.

​
Prerequisites

Before you begin, ensure you have:
  • JumpCloud Administrator access
  • Permissions to create service accounts and custom admin roles in JumpCloud

​
Setup guide

​
Create service account in JumpCloud

1

Access JumpCloud Admin Console

Log in to your JumpCloud Admin Console
2

Navigate to service accounts

Go to Settings > Service Accounts (or User Authentication > Service Accounts depending on your console version)
3

Create a new service account

  1. Click Create Service Account
  2. Enter a name (e.g., “Ravenna”)
  3. Create a custom admin role with the following permissions:
    • Full User Management
    • Full Group Management
    • Device Management (Devices & Mobile Device Management)
  4. Assign the custom role to the service account
  5. Save the service account
4

Generate client credentials

  1. Select the service account you created
  2. Generate a Client ID and Client Secret
  3. Copy both values
Store the Client Secret securely. You will not be able to view it again.
For more details, see JumpCloud’s service account documentation

​
Add integration in Ravenna

1

Navigate to integrations

Go to Settings > Integrations
2

Select JumpCloud

Find JumpCloud in the available integrations and click Connect
3

Select Service Account method

Select Service Account as your authentication method
4

Enter credentials

Provide the following information:
​
string
required
The Client ID from your JumpCloud service account
​
string
required
The Client Secret from your JumpCloud service account
5

Complete setup

Click Add JumpCloud to complete the integration. Ravenna will validate your credentials and begin syncing users and groups.

​
Troubleshooting

Cause: Client ID or Client Secret is incorrect.Solution:
  • Verify the Client ID and Client Secret are copied correctly
  • Ensure there are no extra spaces or characters
  • Confirm the service account is still active in JumpCloud
Cause: The service account lacks the required permissions.Solution:
  • Verify the custom admin role includes Full User Management, Full Group Management, and Device Management
  • Check that the role is assigned to the service account
  • See JumpCloud’s custom admin roles documentation for help configuring roles
Cause: Sync may still be in progress or the service account has limited scope. When the service account can’t read a resource (users, groups, or applications), Ravenna keeps the integration connected and syncs that resource as empty rather than failing.Solution:
  • Allow a few minutes for the initial sync to complete
  • Verify the integration status shows as connected in Settings > Integrations
  • Check that users and groups exist in the JumpCloud organization linked to your credentials
  • Confirm the custom admin role grants read access to each resource type you expect to see, then trigger a resync from the integration page
Last modified on June 25, 2026