Ingest Okta system logs with the new Lakeflow Connect connector

Use cases

Imagine you need to centralize security and user activity events from Okta into your lakehouse for analysis and auditing. With this connector, you can:

• Incrementally ingest Okta system log events.
• Authenticate using SSWS tokens.
• Author pipelines using the API or Declarative Automation Bundles.

How to use

# Example of configuring an ingestion pipeline via API or notebook
pipeline_config = {
    "name": "okta-system-logs-pipeline",
    "connection_id": "my_uc_connection",
    "target": "my_catalog.my_schema"
}

What happens in this code:

1. Sets the name of the ingestion pipeline.
2. Points to the connection created in Unity Catalog.
3. Specifies the target location in the catalog.

Limitations and requirements

• Stage: Beta.
• Requires a workspace admin to turn on Lakeflow Connect for Okta System Logs from the Previews page.
• Supported authentication is exclusively via SSWS API token.
• Only supports incremental ingestion of append-only events.