IBM Content Manager, Version 8.5.0.3

Troubleshooting LDAP integration

Problems with LDAP integration can include problems with the import scheduler and with user authentication.

The following topics provide troubleshooting information about LDAP integration.

Finding the log files that help with LDAP troubleshooting
The integration of Content Manager EE with LDAP involves several different components of Content Manager EE. Therefore, if you discover problems during LDAP integration or after your system is running with LDAP, there are several different log files that you might need to review to diagnose the problems.
Troubleshooting authentication problems with the LDAP user preauthentication tool
The LDAP user preauthentication tool can help you confirm that the LDAP authentication for Content Manager EE is configured correctly.
Running the LDAP user import utility with the correct user privileges
The user that runs the LDAP user import utility must have the proper privileges.
LDAP user import scheduler save function fails
If the creation of the CRON job for the LDAP user import scheduler fails, you can create the CRON job manually.
Problems with the LDAP import utility schedule on non-English Windows operating systems
The LDAP import utility might have problems if the parameters for the Windows AT command are translated.
Scheduled LDAP import does not launch on Windows
If the LDAP import utility does not run as scheduled on Windows, there might be a problem with the setup of the AT service account.
Using log files for problem diagnosis if LDAP user authentication fails
When users cannot log on with LDAP user authentication, there might be errors in the configuration parameters. You can find information about the problem and how to solve it by using the log files.
Resource manager LDAP authentication is failing
A failure of LDAP authentication on the resource manager might be because of expired LDAP access passwords.
Users cannot connect after you import users from LDAP
If LDAP users cannot use IBM® Content Manager workflow, there might be configuration errors in the required products.
Authentication of users fails when using the common name user attribute with Active Directory
Microsoft Active Directory user authentication might fail because of the way that the common name attribute is sometimes used within Active Directory.
Incorrect password entries cause account lockouts earlier than expected
When a user enters an incorrect password during authentication with the LDAP server, the number of authentication attempts allowed by the server is fewer than what is expected by the user. The result might be that a user is locked out of a user account earlier than they expect to be with an incorrect password entry.

Parent topic: Troubleshooting system administration