Okta connector
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Okta from the Previews page. See Manage Databricks previews.
The managed Okta connector in Lakeflow Connect ingests identity and access data from your Okta organization into Databricks. This data includes users, groups, group memberships, app integrations and their assignments, devices, policies, authenticators, and administrator roles.
The connector uses the Okta Management API. To ingest Okta System Log events, use the Okta System Logs connector.
Feature availability
Feature | Availability |
|---|---|
UI-based pipeline authoring |
|
API-based pipeline authoring |
|
Declarative Automation Bundles |
|
Incremental ingestion |
|
Unity Catalog governance |
|
Orchestration using Lakeflow Jobs |
|
API-based column selection and deselection |
|
API-based row filtering |
|
Slowly changing dimensions (SCD) type 2 |
|
Automated schema evolution: New and deleted columns |
|
Automated schema evolution: Data type changes |
|
Automated schema evolution: Column renames |
Requires a full refresh. |
Authentication methods
Authentication method | Availability |
|---|---|
OAuth user-to-machine (U2M) |
|
OAuth machine-to-machine (M2M) |
|
Basic authentication (username/password) |
|
SSWS API token |
An Okta API token that authenticates with the |
Ingest from Okta in 3 steps
Before starting, review the Databricks user persona, supported interfaces, ingestion frequency, and common patterns.
- Configure Okta for ingestion (Admins): Create an Okta API token for Databricks to authenticate with.
- Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer to store credentials for Databricks to authenticate with Okta.
- Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.