About Ldapsearch - 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ā„¢

The following table contains descriptions of the ldapsearch command arguments. For additional information, see Working with Ldapsearch.

Command Arguments Description
-b " " Specifies the search base. Because the RootDSE object has no name, the argument passes a zero-length string.
-D Directory user ID in the form of a dn.

Use only when ldapsearch specifies simple binding (-x).

-H ldap://esroot Identifies the binding scheme and the directory server name.
namingContexts Limits the output of the ldapsearch and does not return other information.
-s base Specifies the scope of the search, from among three choices:
  • base
  • one
  • sub

The examples use base to indicate that the scope is the base.

-U The SASL user ID.

Use this argument to specify the user ID only when also specifying -Y DIGEST-MD5 binding.

-W Requests a prompt for entry of the password for the user.
-x Specifies simple binding for the ldapsearch.

The binding method specified for ldapsearch is independent of the binding method you use generally for LDAP authentication.

-Y DIGEST-MD5 Specifies DIGEST-MD5 binding for the ldapsearch.
The binding method specified for ldapsearch is independent of the binding method you use generally for LDAP authentication.
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.
-Z Requests TLS protection. The directory server may or may not grant the request, and if not, the connection runs in plain text. To demand TLS protection, use -ZZ.