Okta User Directory
Pulls user data from Okta, including metadata for authentication and identity correlation purposes.
Sync Type: Full Synchronisation
Authentication
This input supports API Key and OAuth 2.0 (service app) authentication. See Okta Authentication for setup instructions and required credentials for each method.
Note: When using OAuth 2.0, ensure the
okta.users.readscope is granted on your service app.
Details
Monad uses the cron field to run this input on specific intervals and returns all users' details, performing a full sync of data each time.
Deactivated users (status DEPROVISIONED) are not collected, because Okta's list users API does not return them by default.
Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below. If using the Oauth flow, the token should be granted the okta.users.read scope.
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
org_url | string | Yes | - | Okta Organization URL. |
use_synthetic_data | bool | No | false | Generate synthetic data for testing, instead of connecting to a real data source. Defaults to an hourly cron schedule for cron-based inputs. |
rate_limit | object | No | - | Maximum outbound source-API request rate. A blank or zero value falls back to the connector's default rate-limiting behavior. Maximum 10 requests per second. See API Rate Limiting for the field format. |
cron | string (cron) | Yes | 0 * * * * | Cron string for scheduling the ingest of your input. eg: 0 0 * * * - Daily at midnight, or */15 * * * * - Every 15 minutes. Defaults to an hour. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
api_key | secret | No | Okta API Key. |
rsa_private_key | secret | No | RSA Private Key for OAuth 2.0 authentication with Okta. |
client_id | secret | No | OAuth 2.0 Client ID for Okta application. |
key_id | secret | No | Key ID (kid) for the RSA key pair used in OAuth 2.0 authentication. |
Secrets vary by authentication method. See Okta Authentication for details.
Related Articles
- https://help.okta.com/en-us/content/topics/security/api.htm
- https://developer.okta.com/docs/reference/api/users/
Sample Record
Code
Sync frequency
This input runs on a cron schedule (default hourly, 0 * * * *), which you can configure on the pipeline.
See Input Sync Frequency for details.
Community transforms
The Monad Transforms Repository has ready-made transforms for this input. Import one into your organization, then add it to a pipeline after this input.
| Format | Transform |
|---|---|
| OCSF v1.9.0 | Okta Users to OCSF v1.9.0 |
| ECS v9.5.0 | Okta Users to ECS v9.5.0 |
| CEF | Okta Users to CEF |
CEF transforms emit an intermediate record; add the CEF Serializer transform after one to produce the CEF:0 string.