Resolving problems with the LDAP directory server
If you are having problems with password authentication, verify that you completed all of the configuration steps correctly.
For more information about configuration, see Authenticating users by using an Active Directory database.
After you install the Tivoli® Storage Manager V6.3.3 or later server, or the IBM Storage Protect 7.1.3 or later server, you must configure the LDAP directory server to communicate with the server.
If
you have connection problems, complete the following steps with an
LDAP utility such as ldapsearch or ldp.exe:
- Test forward- and reverse-DNS lookup of the LDAP server system on the server system.
- Test the network connection between the server operating system and the LDAP directory server operating system.
- Connect to the LDAP directory server with the host name and port that you specified in the LDAPURL option.
- Establish a Transport Layer Security (TLS) connection by issuing the following command with
StartTLS
option:
openssl s_client -connect ldaphostname:389 -showcerts -CAfile rootca.crt -starttls ldap - Use simple bind authentication to authenticate with the parameters that you defined for the LDAPUSER and the LDAPPASSWORD.
- Search the LDAP directory server for the BaseDN that you specified in the LDAPURL option.
An LDAP server administrator might use the ldapsearch utility,
as follows, to troubleshoot LDAP directory authentication problems:
- Using OpenLDAP (specify the certificate file using the TLS_CACERT option in the ldap.conf file)
- Without SSL/TLS
ldapsearch -H <hostname> -D <LDAPUSER> -W -s base -b <BaseDN from LDAPURL> -v -x objectclass="*"- With SSL/TLS
ldapsearch -H <hostname> -D <LDAPUSER> -W -s base -b <BaseDN from LDAPURL> -v -x -ZZ objectclass="*"- Using the LDAP client (installed with AIX® or downloaded from ibm.com®)
- Without SSL/TLS
ldapsearch -h <hostname> -D <LDAPUSER> -w ? -s base -b <BaseDN from LDAPURL> -v objectclass="*"- With SSL/TLS
ldapsearch -h <hostname> -D <LDAPUSER> -w ? -s base -b <BaseDN from LDAPURL> -v -Y -x -K "cert.kdb" objectclass="*"
- hostname = the URL from the LDAPURL option,
for example
ldap://ldap.ibm.com:389/ - LDAPUSER = the parameters from the SET
LDAPUSER command, for example
cn=tsmserver,cn=users,dc=ibm,dc=com - BaseDN from LDAPURL = the Base DN from the LDAPURL option,
for example
"OU=tsm,DC=ibm,DC=com"