For context on getting started with ingestion, check out our metadata ingestion guide.
To install this plugin, run
pip install 'acryl-datahub[okta]'.
This plugin extracts the following:
- Group Membership
from your Okta instance.
Usernames serve as unique identifiers for users on DataHub. This connector extracts usernames using the "login" field of an Okta User Profile. By default, the 'login' attribute, which contains an email, is parsed to extract the text before the "@" and map that to the DataHub username.
If this is not how you wish to map to DataHub usernames, you can provide a custom mapping using the configurations options detailed below. Namely,
This connector also extracts basic user profile information from Okta. The following fields of the Okta User Profile are extracted
and mapped to the DataHub
- display name
- first name
- last name
- country code
Group names serve as unique identifiers for groups on DataHub. This connector extracts group names using the "name" attribute of an Okta Group Profile. By default, a URL-encoded version of the full group name is used as the unique identifier (CorpGroupKey) and the raw "name" attribute is mapped as the display name that will appear in DataHub's UI.
If this is not how you wish to map to DataHub group names, you can provide a custom mapping using the configurations options detailed below. Namely,
This connector also extracts basic group information from Okta. The following fields of the Okta Group Profile are extracted and mapped to the
This connector additional extracts the edges between Users and Groups that are stored in Okta. It maps them to the
associated with DataHub users (CorpUsers). Today this has the unfortunate side effect of overwriting any Group Membership information that
was created outside of the connector. That means if you've used the DataHub REST API to assign users to groups, this information will be overridden
when the Okta source is executed. If you intend to always pull users, groups, and their relationships from your Identity Provider, then
this should not matter.
This is a known limitation in our data model that is being tracked by this ticket.
As a prerequisite, you should create a DataHub Application within the Okta Developer Console with full permissions to read your organization's Users and Groups.
You can use the following recipe to get started with Okta ingestion! See below for full configuration options.
source: type: okta config: # Coordinates okta_domain: "dev-35531955.okta.com" # Credentials okta_api_token: "11be4R_M2MzDqXawbTHfKGpKee0kuEOfX1RCQSRx99" sink: # sink configs
For general pointers on writing and running a recipe, see our main recipe guide.
Note that a
. is used to denote nested fields in the YAML configuration block.
|string||✅||The location of your Okta Domain, without a protocol. Can be found in Okta Developer console.|
|string||✅||An API token generated for the DataHub application inside your Okta Developer Console.|
|bool||Whether users should be ingested into DataHub.|
|bool||Whether groups should be ingested into DataHub.|
|bool||Whether group membership should be ingested into DataHub. ingest_groups must be True if this is True.|
|string||Which Okta User Profile attribute to use as input to DataHub username mapping.|
|string||A regex used to parse the DataHub username from the attribute specified in |
|string||Which Okta Group Profile attribute to use as input to DataHub group name mapping.|
|string||A regex used to parse the DataHub group name from the attribute specified in |
|bool||Whether to ingest users in the DEPROVISIONED state from Okta.|
|bool||Whether to ingest users in the SUSPENDED state from Okta.|
|number||The number of entities requested from Okta's REST APIs in one request.|
|number||Number of seconds to wait between calls to Okta's REST APIs. (Okta rate limits). Defaults to 10ms.|
Validated against Okta API Versions:
Validated against load:
Group Membership Edges:
1000(1 per User)
Run Time (Wall Clock):
If you've got any questions on configuring this source, feel free to ping us on our Slack!