r10 - 2015-01-23 - 17:54:23 - StevenBeardYou are here: TWiki >  Deployment Web > DeploymentAdminstering > ConfiguringAndTuningLDAP

uc.png Configuring and tuning Lightweight Directory Access Protocol (LDAP)

Authors: DanToczala
Build basis: CLM 2011 (product versions 3.x) and later

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.

Related topics: None

External links:
  • None

Additional contributors: None

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r10 < r9 < r8 < r7 < r6 | More topic actions
Deployment.ConfiguringAndTuningLDAP moved from Deployment.TuningLDAP on 2013-11-30 - 22:31 by StevenBeard -
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project