1Password connector
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Preview
9.4+
Preview since 9.4
The 1Password connector uses the 1Password Users API to manage users in a 1Password Enterprise Password Manager account. It enables security teams to automate identity-level response actions — such as suspending compromised users — directly from Elastic Security workflows.
You can create connectors in Stack Management > Connectors. For example:
1Password connectors have the following configuration properties:
- Account UUID
- The UUID of your 1Password account. You can find this in the 1Password admin console.
- Client ID
- The OAuth 2.0 Client ID for your 1Password integration.
- Client Secret
- The OAuth 2.0 Client Secret for your 1Password integration.
The connector authenticates using the OAuth 2.0 Client Credentials flow with client_secret_basic authentication. The token URL and scope are derived automatically.
You can test connectors as you're creating or editing the connector in Kibana.
The 1Password connector has the following actions:
- List Users
-
List users in the 1Password account, optionally filtered by state.
- filter (optional): Filter expression —
user.isActive()oruser.isSuspended(). Omit to return all users. - maxPageSize (optional): Maximum number of users to return in a single response, from 1 to 1000. Defaults to 25.
- pageToken (optional): Token to fetch the next page of results.
- filter (optional): Filter expression —
- Get User
-
Retrieve details for a single user by their UUID.
- uuid (required): The UUID of the user.
- Suspend User
-
Suspend an active user, preventing them from accessing the 1Password account. Vault access configuration remains intact.
- uuid (required): The UUID of the user to suspend.
- Reactivate User
-
Reactivate a suspended user, restoring their access to the 1Password account.
- uuid (required): The UUID of the user to reactivate.
Use the Action configuration settings to customize connector networking configurations, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use xpack.actions.customHostSettings to set per-host configurations.
To use the 1Password connector, you need OAuth 2.0 client credentials from a 1Password Enterprise Password Manager account:
- Log in to your 1Password account as an Admin, Owner, or Security group member.
- Navigate to Integrations > OAuth Applications and create a new application.
- Configure the application with the required scopes: List users, List user, Suspend user, Reactivate user.
- Save the Client ID and Client Secret. You will not be able to retrieve the secret later.
- Copy your Account UUID from the admin console URL or account settings.
- When configuring the connector in Kibana, enter the Account UUID, Client ID, and Client Secret.