---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Create a Teradata connection

# Create a Teradata connection {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
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 AllWorkflow Data Fabric HubAvailable connectorsPrimary connectors.
   * Navigate to AdminWorkflow Data Fabric HubAvailable connectorsPrimary connectors.
   {#create-teradata-connection__choices_n5p_vrt_k2c}
2. Find the Teradata connector and select Connect.
3. On the form, fill in the fields.  
   {#create-teradata-connection__table_kmx_fw1_2fc__entry__2}

   | 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: <kbd class="ph userinput">jdbc:teradata://&lt;host&gt;:&lt;port&gt;;database=&lt;databaseName&gt;</kbd> |
   | Authentication methods ||
   | Authentication method | Authentication method to use with Teradata. The available options are: * Basic Authentication (the default) * Bearer Token * OAuth {#create-teradata-connection__ul_x2m_b1t_bjc} |
   | 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. |
   [Table 1. New Teradata Connection form]

   {#create-teradata-connection__table_kmx_fw1_2fc}
4. Select Connect.

## Result

A test connection is made to the external data source, verifying that the connection details are correct and the data source is accessible.

## What to do next

If the connection succeeds, configure data steward access on the Access Control tab. See [Manage access to an established connection using roles](https://www.servicenow.com/docs/lH57CuH3kSJT8KypBiimsA "Manage which data stewards can access an established connection and create data fabric tables.").

If the connection fails, verify the connection details with your data source administrator and try again.

*[\>]: and then