16.00 - External Authentication Configuration - Teradata Unity

Teradata Unity Installation, Configuration, and Upgrade Guide for Customers

prodname
Teradata Unity
vrm_release
16.00
created_date
March 2017
category
Administration
Configuration
Installation
featnum
B035-2523-037K

Unity acts as a proxy to the database in providing External Authentication, LDAP, Kerberos and SPNEGO support.

The proxy mechanism is only available to Unity. Clients cannot use proxy mechanisms to logon to Teradata Database or Unity. The proxy connection only allows Unity to manage user logons to Teradata Database.

Proxy configuration is required on Unity and Teradata Database:
  • With managed Teradata Databases 14.10 or later.
  • If you are using LDAP, Kerberos and SPNEGO. These mechanisms are supported only through proxy.
  • If you are using Network Security Policy.
  • If you are using External Authentication with TD2.

If proxy is configured, Unity uses Client selected mechanism (TD2, LDAP, Kerberos or SPNEGO) from Client to Unity, and proxy mechanisms from Unity to Teradata on behalf of the Client.

You do not have to configure proxy on Unity and Teradata Database if you are using TD2, without External Authentication, to managed Teradata Databases 13.10 to 14.0.

If proxy is not configured with Teradata Database 13.10 to 14.0, Unity connectsTD2 from Client to Unity to Teradata. TD2 with managed Teradata Database 14.10 or later will require proxy.