Okta System Logs connector FAQ
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.
These answers cover supported data, historical availability, authentication, and destination naming for the managed Okta System Logs connector. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which source tables does the connector support?
The connector supports the system_logs table in the default source schema. It doesn't ingest other Okta API resources. For details, see Supported source tables.
How far back can the connector ingest data?
The first pipeline update requests events from the previous 90 days. Okta doesn't return System Log events older than 90 days. Later updates incrementally ingest events published after the last update.
Which authentication method does the connector support?
The connector supports an SSWS API token only. It doesn't support OAuth U2M, OAuth M2M, or username and password authentication.
How is the destination table named?
Set destination_table in the pipeline definition to choose a name. If you omit destination_table, the connector uses the source table name, system_logs.