16.10 - Implementing Simple Binds - Teradata Database

Teradata Database Security Administration

Product
Teradata Database
Release Number
16.10
Release Date
June 2017
Content Type
Administration
Security
Publication ID
B035-1100-161K
Language
English (United States)
  1. Set the LdapClientMechanism property to “simple” on Teradata Database nodes and on the Unity server, if used. See LdapClientMechanism.
    If you use Option 3: Non-LDAP External Authentication with Directory Authorization, TDGSS ignores the setting for this property and automatically implements a simple bind.
  2. When you implement simple binds and the directory does not support the use of simple user names in the logon string for the bind DN, do one of the following:
    • If LDAP can create the user DN from the simple user name without searching the directory, you can employ an identity map as a template to substitute data from the simple username and create the DN. See Using Identity Mapping.
    • If the directory contains a divergent user location scheme, implement the identity search option, which allows Teradata Database to search the directory for the DN. See Using Identity Searches.
      The identity search option also requires configuration of service binding. See Using Service Binds.
Teradata strongly recommends that sites using simple binds also configure SSL or TLS protection, as shown in SSL/TLS Protection Options.