17.20 - Working with LDAPv3-Compliant Directories - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
  • 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 valid, 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 Support if you need to use an uncertified LDAP-compliant directory.