Working with LDAPv3-Compliant Directories - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantageā„¢
  • 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 Vantage users on these uncertified directories. See Using Native Directory Schema to Provision Directory Users.
    • Authentication of Vantage users by an uncertified LDAPv3-compliant directory must use simple binding. See LDAP Binding Options.

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