Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Okta from the Previews page. See Manage Azure Databricks previews.
This page answers frequently asked questions about the managed Okta ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports 25 tables in the default source schema. These tables cover users, groups, group memberships, app integrations and their assignments, devices, policies and policy rules, identity providers, network zones, authenticators, and administrator roles. For details, see Supported source tables.
How far back can the connector ingest data?
For incremental tables, the first sync ingests records changed in the previous 365 days, and each later sync ingests records changed after the last run. To ingest older records, set the start_datetime option. Full-refresh tables reingest all available records on every run.
Which authentication methods does the connector support?
The connector supports an SSWS API token only. It doesn't support OAuth user-to-machine (U2M), OAuth machine-to-machine (M2M), or username and password authentication.
Does the connector capture deleted records?
Full-refresh tables drop deleted records on the next sync. Incremental tables keep deleted records until a full refresh, because Okta doesn't report deletions. When a user is deactivated, Okta sets the user's status to DEPROVISIONED, and the users table shows the status change.
Does the connector ingest System Log events?
No. To ingest Okta System Log events, use the Okta System Logs connector.