Specifying a Binding Method for an ldapsearch - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2022-02-15
dita:mapPath
ppz1593203596223.ditamap
dita:ditavalPath
wrg1590696035526.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantageā„¢

The directory must authenticate the user that executes the ldapsearch command before it allows the user access to site information. The command must specify one of the following sets of authentication information, depending on the binding scheme the directory uses for user authentication.

Binding Method ldapsearch Options Description
Simple -x -D user_principal_name -W -ZZ
  • -x, -D, -W and -ZZ specify simple binding and associated protection.
  • user_principal_name identifies (in UPN form) the user running the command, for example:

    user@domain

DIGEST-MD5 [Deprecated] -Y DIGEST-MD5 -U simple_user_name
  • -Y DIGEST-MD5 specifies the binding type
  • -U is the simple user name, derived from the directory sAMAccountName attribute
The DIGEST-MD5 authentication protocol used by LDAP is deprecated. Teradata strongly recommends you use simple binding with TLS protection, and stop using DIGEST-MD5.