LDAP configuration should be relatively straightforward in most cases.
Common LDAP mistakes
Some customers have seen poor performance when they use LDAP authentication using an LDAP resource that is remote and has a poor connection to the Jazz infrastructure. Long latency between your LDAP resource and the Jazz deployment can lead to lengthy login times, and odd Jazz application "stalls", when the user needs to be reauthenticated.
Keep in mind that you have the ability to modify the LDAP queries used to authenticate users in the Jazz Team Server (JTS) administration console.
The nightly synchronization of user data between the LDAP repository and the JTS uses the LDAP queries specified in the JTS administration console
Debugging LDAP issues
Seeing strange LDAP behavior? If you are on Windows, try the free Softera LDAP browser. It will allow you to see and visualize what is going on with the LDAP in the customer environment. If your customer is using Linux, try the Luma LDAP browser out on SourceForge.