JumpCloud

JumpCloud is a cloud-based directory platform that unifies Active Directory and LDAP services with a focus on user authentication and network management. It allows organizations to manage and provision user access to software, systems, networks. For detailed information refer to the JumpCloud official documentation.

Integration Method: API

Tables: Account Change (3001), Authentication (3002)

This integration supports the following type of events.

This integration supports the following versions.

Prerequisites

• The user should have access to the JumpCloud portal with an account that has the Administratorprivileges.

• The user should have access to the DataBee console.

Configuration Overview

1. Generate an API token after logging in to JumpCloud Admin console.

2. Add the JumpCloud data feed integration in the DataBee console with the required API token.

   DataBee Parameter	JumpCloud Parameter
   Token	API Key

JumpCloud Configuration

1. Log in to JumpCloud Admin console.

2. In the Admin Portal, click your account initials in the top-right corner and select Administrators.
    

3. Click on the Admin Name as shown below. Please note that the Admin name will be the username that was used to login earlier.

   

4. In the “Edit Administrator”window, click on the check box Enable API access.

   

5. Log out from the JumpCloud account and log in again. Click on your account initials and select My API Key.

   

6. Click on Generate New API Key and select ‘Expiration Date’ as 90 days.

   

7. Copy the generated API Key and save it for later use.

   
   

   Note:

   Copy and Save the API Key and the key will expire in 90 days, you will have to generate them again and reconfigure the data feed in DataBee as well.

DataBee Configuration

1. Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Feed button.
    

   

2. Search for Jumpcloud and click it as shown below.

   

3. Click on the API Ingest option for the collection method.

   
   

4. Enter feed contact information and scroll down.

   
   

5. Include Feed in Entity Resolution: Enable this option to include the feed in the entity resolution process. A checkbox for this field is auto-enabled for all new feeds. You can deselect it to exclude the feed from entity resolution.

   • Full Entity Resolution: Automatically creates and updates entities when they are discovered in the data.

   • Associate Only: Links new events to existing entities without modifying their attributes.

   A checkbox is available for each entity type (user, device, application, and cloud resource) to select the desired level of resolution (Full Entity Resolution, Associate Only).

6. Environment: There are two options for Environment - Production or Staging. This is refers to different areas in the data lake where the feed should store data to.

   • The Staging environment is a temporary area in the data lake where the feed output and mapping can be evaluated and tested. It will not affect dashboard data.

   • By selecting Production, the feed data will be available for use within the dashboards and other derivative tables.

   

7. In the configuration page, confirm the following:

   • API Base URL: this is the base URL that DataBee will interact with.

   • Authorization Method: Bearer Token

   • Token: paste the API KEY generated earlier in the JumpCloud console.

   • Event types: preselected for all the events types the integration pulls.

   

8. Click Debug Test Connection to verify your credentials. A Connection successful! message confirms that DataBee can reach the JumpCloud API with the credentials provided.

9. Click Save Draft to save your current changes.

10. Click Submit to complete the configuration process.

Troubleshooting Tips

• Ensure the token is pasted correctly. Since you cannot view the token after the 1st time, re-create the token, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.