1Password
Sign In Attempts
Retrieves 1Password sign in attempts for activity monitoring.
Sync Type: Full Synchronisation
Requirements
- Before you connect Monad to 1Password, you need admin access to a 1Password account, and an appropriate plan that supports audit log access.
- Once you have access, you need to create a Bearer token following these steps: https://support.1password.com/events-reporting/#appendix-issue-or-revoke-bearer-tokens. Ensure auditevents permissions on the token. This token is long lived.
- Once done, you need to figure out your Base URL for your account for Monad to connect to. Find more info about the same here: https://developer.1password.com/docs/events-api/servers/
Details
Monad uses the timestamp as a part of the query parameters on the API to determine what events to display. This field is updated every time a request to get events is successful with the time of the latest event generated. If this was the first time requesting for events, a full sync of the data is performed.
Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.
Settings
| Setting | Type | Required | Description |
|---|---|---|---|
| Base URL | string | No | The base URL for your 1Password account. |
| Backfill Start Time | string | No | The date to start fetching data from. If not specified, no past records will be fetched. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
| Bearer Token | string | Yes | Bearer token for 1Password API. This is required to authenticate requests. |
Related Articles
Sample Record
Code
Last modified on