Actions for Okta #
- Send Data to Okta. Sends a custom set of Lucidum data to Okta.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to Okta on a regular schedule.
- You can send normalized, enriched Lucidum data to Okta to be indexed, searched, and analyzed.
Prerequisites #
To execute Okta actions, you must:
- Configure a Okta API connection beforehand. The required parameters are described in the instructions for creating a Okta connector in Lucidum https://lucidum.io/docs/okta-sso/.
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
Okta Configuration #
To create a configuration for Okta actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
-
URL. The base URL of the Okta server. For example, https://lucidum.okta.com
-
API Token. The API token for an account that has read and write access to the Okta APIs.
- Max # of Records per Payload. The maximum number of records to send to Okta in each action. The default value is “50”.
Create a New Action #
To create an action for Okta, contact Lucidum customer care.
