# Database Hub authentication

> To create a Database Hub connection, you need credentials specific to the database you are
connecting to. Depending on the database type, these may include:

## Prerequisites

To create a Database Hub connection, you need credentials specific to the database you are
connecting to. Depending on the database type, these may include:

* **SQL Server / PostgreSQL / Amazon Redshift**
  * Database host
  * Username
  * Password
  * Database and schema
* **Oracle**
  * Database host
  * Username
  * Password
  * Service 
  * Schema
* **Snowflake**
  * Database host
  * Username and password
  * Warehouse, database, and schema
  * Role
* **Databricks**
   * For **Personal Authentication Token (PAT)** authentication:
      * Database host
      * HTTP path
      * Personal access token
      * Catalog Name
      * Schema Name
   * For **OAuth Client Credentials** authentication:
      * Database host
      * HTTP path
      * Client ID
      * Client Secret
      * Catalog Name
      * Schema Name

   :::note
   * Databricks connections are supported for both Databricks on Azure (`*.azuredatabricks.net`) and `cloud.databricks.com`.
   * When connecting to Databricks, the connector includes a User-Agent header value of `uipath+uipath` with each request. This identifier helps Databricks and administrators trace requests to UiPath in audit and diagnostic logs.
   :::

Refer to your database provider’s documentation for details on retrieving these values.

## Add the Database Hub connection

1. Select Orchestrator from the product launcher.
2. Select a folder, and then navigate to the **Connections** tab.
3. Select **Add connection**.
4. To open the connection creation page, select the connector from the list. You can use the search bar to find the connector.
5. Select your database type (for example, SQL Server, Databricks, Snowflake).
6. Enter the required credentials (for example, host, username, password, database name/schema).

   For any secret-type field, you can select the menu next to the field and choose **Use credential asset** to reference an Orchestrator credential asset linked to an external vault instead of entering the value directly. For more information, see [Use credential assets for connections](credential-store-connections.md).
7. Optionally, for SQL Server and PostgreSQL connections, select **Enable TLS (Encrypted Connection)** to require an encrypted connection to the database. When enabled:
   * For PostgreSQL, select an **SSL Mode**:
      * **Require** — Always use SSL. Connection fails if the server does not support SSL.
      * **Allow** — Use SSL if the server supports it; otherwise fall back to an unencrypted connection.
      * **Disable** — Never use SSL.
   * For SQL Server, select whether to **Ignore SSL Errors**. Set to **True** to skip SSL certificate validation (use only for testing, this is not recommended for production).
   
   :::note
   TLS is always enabled for Amazon Redshift.
   :::
8. Select **Connect**.

Your Database Hub connection has now been added and is available for use in UiPath Studio or Studio Web.