Troubleshoot the 1Password Event Logs connector

Beta

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.

Resolve common 1Password Event Logs connector errors, including authentication failures from an invalid bearer token and requests sent to the wrong Events API host.

For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.

Pipeline fails to authenticate

Cause: 1Password rejected the bearer token. The token might be missing, expired, revoked, or issued for a different Events Reporting integration.

Solution:

1. Confirm that the Bearer token in the Unity Catalog connection matches an active Events Reporting token in 1Password.
2. Issue a new token if the previous token was revoked or has expired. When you edit the connection, enter the new token. The form does not reuse the stored secret.
3. Confirm that the token includes the event types you ingest: audit events, item usages, and sign-in attempts.

For details, see Configure authentication to 1Password.

Requests fail because of the Events API host

Cause: The Base URL does not match the Events API host for your account region, or it includes an https:// prefix that the connection does not expect.

Solution:

1. Set Base URL to the host only, for example events.1password.com, events.1password.ca, or events.1password.eu.
2. Confirm the host for your account in the 1Password Events API documentation.

1Password API temporarily unavailable

Cause: 1Password returned a transient server error.

Solution:

The connector retries failed requests. If the issue persists, wait, then run the pipeline again.