Actions for JumpCloud #
- Send Data to JumpCloud. Sends a custom set of Lucidum data to JumpCloud.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to JumpCloud on a regular schedule.
- You can send normalized, enriched Lucidum data to JumpCloud to be indexed, searched, and analyzed.
Prerequisites #
To execute JumpCloud actions, you must:
- Configure a JumpCloud API connection beforehand. The required parameters are described in the instructions for creating a JumpCloud connector in Lucidum https://lucidum.io/docs/jumpcloud/.
NOTE. The specified account should have read and write permissions.
Workflows #
- Creating a new Configuration and a new Action
- Cloning an Existing Action
- Creating a new Action from the Location Results page
- Editing a Configuration
- Editing an Action
- Viewing Information about an Action
JumpCloud Configuration #
To create a configuration for JumpCloud actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- URL. Base URL for JumpCloud. For example, console.jumpcloud.com
-
Events API URL. URL for the JumpCloud Event API. For example, https://api.jumpcloud.com/insights/directory/v1/events
-
API Key (required). API key for a JumpCloud account with read and write access to API data. (Lucidum currently supports JumpCloud V1 API). For details on generating a new API key, see https://docs.jumpcloud.com/api/1.0/index.html#section/API-Key or https://jumpcloud.com/support/jumpcloud-apis#accessing-your-api-key.
-
Max # of Records per Payload. The maximum number of records to send to JumpCloud in each action. The default value is “50”.
Create a New Action #
To create an action for JumpCloud, contact Lucidum customer care.
