Register a Teradata Connection
Requirement
Teradata VantageCloud or Teradata VantageCore
Permissions
The user registering the connection must have the permissions below.
APPLICATION_ADMINImmuta permissionThe Teradata user registering the connection must have the following privilege:
DBADMIN
Create the database user
Create a new user in Teradata to serve as the Immuta system account. Immuta will use this system account continuously to crawl the connection.
Grant this account the following Teradata privileges:
SELECTon the DBC databaseCREATE ROLEDROP ROLESELECT WITH ADMIN OPTIONon all Teradata views that Immuta should manage permissions to
Register a Teradata connection
In your Teradata environment, create an Immuta database that Immuta can use to connect to your Teradata instance to register the connection and maintain state with Teradata.
Having this separate database for Immuta prevents custom ETL processes or jobs deleting the database you use to register the connection, which would break the connection.
In Immuta, click Data and select Connections in the navigation menu.
Click the + Add Connection button.
Select the Teradata tile.
Enter the host connection information:
Display Name: This is the name of your new connection. This name will be used in the API (
connectionKey), in data source names from the host, and on the connections page.Hostname: Your Teradata host (e.g.,
your-host.env.teradata.com)Port: Port configured for Teradata.
Database: The Teradata database you created for Immuta. All databases in the host will be registered.
SSL Mode: Use the dropdown to select your SSL mode.
SSL Protocol: Based on your SSL mode selection, also select the protocol.
Select the authentication method from the dropdown:
Username and Password or LDAP: Enter the username and password of the Teradata user you created above.
OAuth: Enter the authentication details of the Teradata user you created above.
Fill out the Client ID, which is the subject of the generated token. It is also known as
sub(subject).Fill out the Client Secret.
Fill out the Authority URL of your identity provider.
Enter the Scope to limit the operations and roles allowed in Teradata by the access token. See the OAuth 2.0 documentation for details about scopes.
Click Save connection.
Map users
Requirement: USER_ADMIN Immuta permission
Map Teradata usernames to each Immuta user account to ensure Immuta properly enforces policies.
The instructions below illustrate how to do this for individual users, but you can also configure user mapping in your IAM connection on the app settings page.
Click People and select Users in the navigation menu.
Click the user's name to navigate to their page and scroll to the External User Mapping section.
Click Edit in the Teradata User row.
Select the User Type from the dropdown:
Teradata Username: Enter the user's Teradata username.
Unset (fallback to Immuta username): When selecting this option, the Teradata username is assumed to be the same as the Immuta username.
None (user does not exist in Teradata): When selecting this option,
Click Save.
Last updated
Was this helpful?

