Okta System Logs connector

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Okta System Logs from the Previews page. See Manage Databricks previews.

The managed Okta System Logs connector in Lakeflow Connect ingests audit and security events from your Okta organization into Databricks.

The connector uses the Okta System Log API to ingest append-only events, including user activity, authentication, security, and configuration changes.

Feature availability

Feature	Availability
UI-based pipeline authoring	Not supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Not supported Okta System Log events are append-only.
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Supported Treated as a new column (new name) and deleted column (old name).

Feature	Availability
UI-based pipeline authoring	Not supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Not supported Okta System Log events are append-only.
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Supported Treated as a new column (new name) and deleted column (old name).

Authentication methods

Authentication method	Availability
OAuth U2M	Not supported
OAuth M2M	Not supported
Basic authentication (username/password)	Not supported
SSWS API token	Supported

Authentication method	Availability
OAuth U2M	Not supported
OAuth M2M	Not supported
Basic authentication (username/password)	Not supported
SSWS API token	Supported

What to know before you start

note

Before starting, review the Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

Start ingesting from Okta

1. Configure Okta for ingestion (Okta admins). Create an SSWS API token for Databricks.
2. Create a Unity Catalog connection (Admins). Create a connection in Catalog Explorer so pipeline authors don't need direct access to the API token.
3. Create an ingestion pipeline (Admins or non-admins). Use Declarative Automation Bundles or a Databricks notebook to create a pipeline from an existing connection.