1Password Event Logs connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for 1Password Event Logs from the Previews page. See Manage Databricks previews.
Common questions about the managed 1Password Event Logs ingestion connector: supported tables, authentication, and Events API hosts. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports audit_events, item_usages, and sign_in_attempts in the default source schema. For destination schemas, see Destination table schemas.
Which authentication methods does the connector support?
The connector supports a 1Password Events Reporting bearer token only. OAuth U2M, OAuth M2M, and basic authentication with a username and password aren't supported.
Which Events API host should I enter?
Enter the host without an https:// prefix. The default is events.1password.com. Use events.1password.ca or events.1password.eu when your account uses those regions. See the 1Password Events API.
How far back can the connector ingest data?
The first sync starts from the earliest events the Events API returns. Each later sync ingests events after the last cursor on the time field. Retention is controlled by 1Password, not by Databricks.
Does the connector support SCD Type 2?
No. SCD Type 2 is not supported.