# Automatic Data Processing ( ADP )

**Automatic Data Processing**

![ADP-logo.png](https://assets.relyanceuat.xyz/images/docs/36494938290829/36494938277517.png)

ADPis a global technology company that provides cloud-based human capital management (HCM) solutions and business process outsourcing services.

To connect Relyance AI with ADP, you will need a Client Secret, a Client ID and a Certificate Signing Request (CSR).

**In ADP:**

- **Please note:** if you can't find this information, please contact your Client Representative.

1. Log in and navigate to the section for "**Apps**" or "**My Apps**."
2. Click on "**Register App**" or a similar button to create a new application.
3. You will need to provide details about your application, such as name, description, and potentially a callback URL
4. Submit the application.
5. After your application is registered, go to the "**Apps**" section and select the application you just registered.
6. Look for a "Credentials" tab or a section that provides API keys or credentials.
7. There, you should find your **Client ID** and **Client Secret**. These are unique identifiers for your application that you will use to authenticate with the ADP API.

- To get the Certificate Signing Request, please refer to this article: [**Generating a Certificate Signing Request**](https://developers.adp.com/getting-started/key-concepts/generate-a-certificate-signing-request)

**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. Search and locate the **ADP** 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, 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**.
9. In the **Authentication** section, provide the requested fields: **Role** **Code**, **Base** **URL**, **Certificate** (please refer to the tooltips), and the **Client** **Secret** and **Client** **ID**.
10. Review the configuration summary from the **Completion** section and click on **Finish**.
11. Confirm the integration Status reflects **Connected**.

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

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

![Screenshot](https://assets.relyanceuat.xyz/images/docs/36494938290829/36494952025741.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. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
2. **A credential rotated at the vendor is not picked up here.** **Client Secret** 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.
3. **Check the address fields before suspecting the credentials.** **Base URL** 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 |
| --- | --- | --- |
| **Two Legged Oauth2** | `Role Code`, `Base URL`, `Client ID`, `Client Secret` (secret), `Certificate` | — |

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

  auth = {
    method = "oauth-client-credentials"
    params = {
      role_code = "administrator"
      base_url = "<base_url>"
      client_id = "<client_id>"
      certificate = "<certificate>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      client_secret = var.adp_client_secret
    }
    secrets_wo_version = 1
  }

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

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