# Sauce Labs

![SauceLabs-logo.png](https://assets.relyanceuat.xyz/images/docs/6583916748301/6586156793869.png)
Sauce Labs is a widely used cloud-based platform for comprehensive automated and manual testing of desktop and mobile applications. It allows users to run tests in the cloud on more than 700 different browser platforms, operating systems and device combinations.

In order to integrate Sauce Labs with Relyance AI you will need a Sauce Labs **Username** and **Access Key**.

#### In Sauce Labs:

![SauceLabs-1.png](https://assets.relyanceuat.xyz/images/docs/6583916748301/6586329319565.png)
![SauceLabs-2.png](https://assets.relyanceuat.xyz/images/docs/6583916748301/6586438633613.png)
1. Login to your Sauce Labs dashboard.
2. Navigate to **Account**> **User Settings.**

3. Scroll down to find your **Access Key**.

4. Copy the key to be used in Relyance AI.

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Click on the **Vendor Integration** tab.
5. Find the **Sauce Labs** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Custom**.
8. Paste the **Username** and **Access Key** into their respective fields.

![SauceLabs-3.png](https://assets.relyanceuat.xyz/images/docs/6583916748301/6586462531085.png)

The **Authentication** step asks for:

- **Username**: required.
- **Access Key**: required; held as a secret.

9. Click **Authenticate**.
10. At this point, you should see the following result on the Vendor Integrations page:

![SauceLabs-4.png](https://assets.relyanceuat.xyz/images/docs/6583916748301/6586491045773.png)

11. Congratulations, you are now connected to **Sauce Labs**.

<!-- 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" "saucelabs" {
  vendor = "saucelabs"
  name   = "<your connection name>"

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

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

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