# 1Password

![Image 1 of 1](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600070895373.svg)
1Password is a password manager application for authentication to web pages. It can also protect users documents, credit card information, and addresses.

In order to integrate 1Password with Relyance AI you will need an **Access Token** and **Connect Host**.
You will need a business, team, or enterprise subscription with 1Password to use this integration.You will need to be running a **[1Password connect server](https://developer.1password.com/docs/connect)** in order to use this integration. Setting up, configuring, and securing your connect server falls out of scope for this article.

#### In 1Password:

![1Password-1.png](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600070906381.png)
1. Login to your 1Password account. This procedure assumes you already have an *Environment* and associated *Vault* to be used in the integration procedure. Some steps may differ slightly if other access tokens have already been generated for this Environment.
2. Click **Integrations** in the right-hand menu.
3. If you've setup an integration before, you'll be directed to **Active** integrations. Click on the **Directory** tab at the top of the page.
4. On the **Directory** page, click the **Other** button under **Infrastructure Secrets Management**.
5. Fill out the form with the following: **Environment name**: Provide a meaningful name (e.g. Relyance Integration Scan) **Vaults**: Choose each vault you wish to include in the scan.
6. Click **Add Environment**.
7. The next page will help you create an **Access token**. Fill out the form: **Token Name**: Provide a meaningful name (e.g. Relyance Scan) **Expires After**: Provide a timeframe **Vaults**: Chose any vaults you wish to include and set all permissions to 'Read'
8. Click **Issue Token**.
9. On the next page you will be issued a **Credentials File** and **Access Token**.  It is recommended to use the **Save in 1Password** buttons for both items.
10. Save the **Credentials file** and copy the **Access Token** to be used in Relyance.
11. Create a connect server using this guide: [https://developer.1password.com/docs/connect/get-started#step-1-set-up-a-secrets-automation-workflow](https://developer.1password.com/docs/connect/get-started#step-1-set-up-a-secrets-automation-workflow)

![1Password-2.png](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600070909837.png)

![1Password-3.png](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600070910477.png)

![1Password-4.png](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600070911885.png)

![1Password-5.png](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600076931085.png)

#### In Relyance AI:

1. Login to your Relyance account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **1Password** integration card and click on it.
5. Click on the **Add Connection** button on the top right
6. Provide a meaningful name for the integration and click on the **Add** button
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/)
8. In the **Connection** section, provide the appropriate values and click on **Continue**,

![Screenshot 2025-11-06 190100.png](https://assets.relyanceuat.xyz/images/docs/34600076953229/40921189900429.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600070916621.png)

9. In the Authentication section, provide the **Access Token and Connect Host**
10. If the Data Inspection check box is checked from step 7, In the Data Inspection section, provide the appropriate values and click on **Continue** **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600070925709.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600070926861.png)

11. Review the configuration summary from the Completion section and click on Finish.
12. Confirm the integration Status reflects Connected

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34600076953229/34600076935821.png)

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A credential rotated at the vendor is not picked up here.** **Access Token** is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
2. **Check the address fields before suspecting the credentials.** **Connect Host** identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

<!-- failure-modes:end -->

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Custom** | `Access Token` (secret), `Connect Host` | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "1password" {
  vendor = "1password"
  name   = "<your connection name>"

  auth = {
    method = "access-token"
    params = {
      connect_host = "<connect_host>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      access_token = var.1password_access_token
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->