From the Vantage command prompt, use one of the following ldapsearch commands to find the site objects in a domain:
- For simple binding:
ldapsearch -x -D user@domain -W -H ldap://dir_name -ZZ \ -b "CN=Sites,CN=Configuration,DC=domain,DC=COM" -s one "(objectClass=site)" cn - For DIGEST-MD5 binding:
ldapsearch -Y DIGEST-MD5 -U user_name -H ldap://dir_name \ -b "CN=Sites,CN=Configuration,DC=domain,DC=COM" -s one "(objectClass=site)" cnThe DIGEST-MD5 authentication protocol used by LDAP is deprecated. Teradata strongly recommends you use simple binding with TLS protection, and stop using DIGEST-MD5.
where:
| Option | Description |
|---|---|
| -H ldap:// | Specifies the directory scheme. |
| dir_name | Specifies the DNS name of a directory server in the domain, for example, the dir_name in Locating the Configuration Naming Context. |
| -b "CN=Sites,CN=Configuration,DC=DOMAIN1,DC=COM" | Specifies the scope of the search, in this case, all sites in the domain configuration naming context identified in Locating the Configuration Naming Context. |
| -s one "(objectClass=site)" cn | Identifies the parent object one level above the site object class as the search base. |
The ldapsearch command returns output similar to:
# extended LDIF # # LDAPv3 # base <CN=Sites,CN=Configuration,DC=DOMAIN1,DC=COM> with scope oneLevel # filter: (objectClass=site) # requesting: cn # ChicagoDiv, Sites, Configuration, DOMAIN1.COM dn: CN=ChicagoDiv,CN=Sites,CN=Configuration,DC=DOMAIN1,DC=COM cn: ChicagoDiv # NewYorkDiv, Sites, Configuration, DOMAIN1.COM dn: CN=NewYorkDiv,CN=Sites,CN=Configuration,DC=DOMAIN1,DC=COM cn: NewYorkDiv # SanDiegoHQ, Sites, Configuration, DOMAIN1.COM dn: CN=SanDiegoHQ,CN=Sites,CN=Configuration,DC=DOMAIN1,DC=COM cn: SanDiegoHQ # search result search: 2 result: 0 Success
where SanDiegoHQ is the location of a Teradata Vantage system that requires site aware, local authentication of users from other locations.