--- title: Create a Teradata connection description: Establish a zero copy connection to a Teradata system in Zero Copy Connector Hub. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/create-teradata-connection.html release: australia topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Teradata, Primary connectors, Zero Copy Connectors, Workflow Data Fabric] --- # Create a Teradata connection Establish a zero copy connection to a Teradata system in Zero Copy Connector Hub. ## Before you begin Role required: df\_connection\_admin ## About this task Work with your data source admin to create a connection to Teradata. For additional information about connecting to Teradata, refer to the [Teradata documentation](https://github.com/Teradata/trino/blob/teradata-connector/docs/src/main/sphinx/connector/teradata.md) and [Teradata JDBC Driver](https://teradata-docs.s3.amazonaws.com/doc/connectivity/jdbc/reference/current/jdbcug_chapter_2.html). ## Procedure 1. Navigate to the available primary connectors in Zero Copy Connector Hub in one of the following ways: - Navigate to **All** > **Workflow Data Fabric Hub** > **Available connectors** > **Primary connectors**. - Navigate to **Admin** > **Workflow Data Fabric Hub** > **Available connectors** > **Primary connectors**. 2. Find the Teradata connector and select **Connect**. 3. On the form, fill in the fields.
| Field | Description |
|---|---|
| Name and description | |
| Connection label | Unique name for this connection. This helps in identifying the connection within your system. |
| Connection name | System-generated name based on the Connection label. This field cannot be modified once the connection is established. |
| Short description | Description of the connection explaining what it is about. |
| Connection attributes | |
| Connection URL |
JDBC URL to establish the connection. For example:`jdbc:teradata:// |
| Authentication methods | |
| Authentication method | Authentication method to use with Teradata. The available options are: - Basic Authentication \(the default\) - Bearer Token - OAuth |
| Basic Authentication | |
| Database username | User name associated with the database. |
| Database password | Password associated with the user name. |
| Bearer Token | |
| Private Key | Private key used to sign the JWT bearer token for client authentication. |
| JWS Certificate | X.509 certificate PEM file containing the public key corresponding to the private key. Required by identity providers that need an x5t header thumbprint for JWT signature verification. |
| Client Id | Client identifier registered with the identity provider. |
| OAuth | |
| **Note:** The OAuth authentication method supports two credential types, each corresponding to a login mechanism configured on the Teradata side. Confirm the configured mechanism before selecting an option. | |
| OAuth credential type | OAuth credential type to use with Teradata. - Teradata Service Principal: Used for a secret-based login mechanism. - Access Token: Used for a JWT-based login mechanism. |
| Teradata Service Principal fields | |
| Client Id | Client identifier registered with the identity provider. |
| Client Secret | Client secret associated with the service principal. |
| Access Token field | |
| OAuth entity profile | OAuth entity profile associated with the application registry \(oauth\_entity table\) created using the data source or IdP credentials. Token management is handled by the platform's OAuth framework. |