Troubleshooting the LDAP configuration

Edit online

You might need to troubleshoot your LDAP configuration.

Procedure

  1. If some or all of the following conditions are true, your LDAP configuration failed:
    • You can still log in as apmadmin, or as any user defined in basic registry.
    • You get the following error when you attempt to log in to https://host_name:9443
      login failed
    Complete the following checks:
    • Check that the commonRegistry.xml file was updated correctly to point to ldapRegistry.xml.
    • Check that the LDAP server address, port, and bind credential are referenced correctly in the ldapRegistry.xml file. Any edits that you make and save take effect immediately.
    • Check that the correct ID is used in the ldapRegistry.xml file. Typically the uid for Tivoli Director Server or the sAMAccountName for Microsoft Active Directory is a single string with no spaces, and is different from the CN. For example, a user named John Smith might have a uid called johnsmith. The sample ldapRegistry.xml files are set up to use uid or sAMAccountName as the login ID. However, once logged in, the first CN is used to display the user name.
  2. If you need to revert to basicRegistry, complete the steps in Switching from LDAP back to basicRegistry.