16.10 - Working with LDAPv3-Compliant Directories - Teradata Database

Teradata Database Security Administration

prodname
Teradata Database
vrm_release
16.10
created_date
June 2017
category
Administration
Security
featnum
B035-1100-161K
  • RootDSE reads can be done using an anonymous bind or a service bind. For directories that do not allow anonymous binds to the RootDSE, a service bind is done if a service DN is provided. If the Service DN is not specified or its password is not good, the directory must be set up to allow anonymous reads of the RootDSE object.
  • Implementation requirements for uncertified LDAPv3- compliant directories are similar to the requirements for certified directories, with the following exceptions:
    • Teradata directory schema extensions do not support uncertified LDAPv3-compliant directories. You must use native directory schema to implement management of Teradata Database users on these uncertified directories. See Using Native Directory Schema to Provision Directory Users.
    • Authentication of Teradata Database users by an uncertified LDAPv3-compliant directory must use simple binding, rather than the default DIGEST-MD5 binding. See LDAP Binding Options.

      Contact Teradata Professional Services if you need to use an uncertified LDAP-compliant directory.