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.
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 | Description |
|---|---|---|---|
| Org URL | string | Yes | Your Okta Organization URL. |
| Cron | string | Yes | A cron expression defining how often to fetch user data. |
| API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See API Rate Limiting for the field format, limits, and how to choose a value. |
Secrets
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.