# Hive

![Hive_Logo.svg](https://assets.relyanceuat.xyz/images/docs/8047344602509/8046949416461.svg)
Hive is a cloud-based project management and collaboration software. It helps to automate work and optimize processes related to communication and collaboration, task and project management.

In order to integrate Hive with Relyance AI you will need an **API Key** and **User ID**.

#### In Hive:

1. Login to your Hive account.
2. In the top right-hand corner click on the account menu. Select **Edit profile**.
3. In the left-hand navigation menu, click **API info**.
4. Generate an API Key in this page. Copy the **API Key** and **User ID** to be used in Relyance AI.

![Hive-3.png](https://assets.relyanceuat.xyz/images/docs/8047344602509/8047289032589.png)

#### 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 **Hive** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Custom**.
8. Paste the **API Key** and **User ID** into their respective fields.

![Hive-1.png](https://assets.relyanceuat.xyz/images/docs/8047344602509/8047289102221.png)

The **Authentication** step asks for:

- **Host**: required.
- **Port**: required.
- **Database Name**: required.
- **Engine Type (MySQL, MariaDB, Postgres, SQLServer)**: required.
- **Username**: optional.
- **Password**: optional; held as a secret.

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

![Hive-2.png](https://assets.relyanceuat.xyz/images/docs/8047344602509/8047272858381.png)

11. Congratulations, you are now connected to **Hive**.

<!-- 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.** **Password** 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.** **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 |
| --- | --- | --- |
| **RDBMS** | `Host`, `Port`, `Database Name`, `Engine Type` | `Username`, `Password` (secret) |

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

  auth = {
    method = "username-password"
    params = {
      endpoint = "<endpoint>"
      port = "<port>"
      database = "<database>"
      engine = "<engine>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      password = var.apache_hive_password
    }
    secrets_wo_version = 1
  }

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

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