17.10 - Sample Configuration for Mutual Authentication - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Release Date
July 2021
Content Type
Administration
Security
Publication ID
B035-1100-171K
Language
English (United States)

The following example shows a typical TdgssUserConfigFile.xml update to support TLS mutual authentication on the LDAP mechanism. Configuration of the KRB5 or SPNEGO mechanism is similar.

<Mechanism Name="ldap">
    <MechanismProperties
        ...
        LdapClientTlsCert="/opt/teradata/tdat/tdgss/site/ssl/certs/clientcert.pem"
        LdapClientTlsKey="/opt/teradata/tdat/tdgss/site/ssl/certs/clientkey.pem"
        />
</Mechanism>

After you add the client certificate and key to the TdgssUserConfigFile.xml, and run the run_tdgssconfig utility in the TDGSS bin directory, you can test the setup with tdgssauth. See Working with tdgssauth.

Make sure to verify the configuration on each Vantage node and on the Unity server, if used. Failure to adequately test the configuration can result in loss of connectivity for Vantage clients using LDAP authentication.

After you verifying the results, restart Teradata Vantage to enable the new configuration.