Multiple failed ClearQuest Web logins can lock LDAP accounts
This technote identifies an IBM® Rational® ClearQuest® Web defect relating to the locking of domain accounts when using LDAP authentication.
This problem happens when using LDAP authentication with ClearQuest. The LDAP server locks an account after a defined number of failed login attempts. Users may experience LDAP/domain account locking when incorrectly logging into ClearQuest Web, even though the failed attempts do not exceed the configured limits of the LDAP server.
There are two LDAP login efforts when one failed ClearQuest Web login occurs. This can result in an unexpected account locking if enough invalid attempts reach the LDAP server. This issue was identified as a product defect under APAR PK74842.
Resolving the problem
This problem is fixed starting in ClearQuest versions 22.214.171.124, 126.96.36.199, and 188.8.131.52. Upgrade to the latest version of ClearQuest to resolve this issue.
|Software Development||Rational ClearQuest||Web Java Client|
|Software Development||Rational ClearQuest||Web Client (7.1)|
More support for:
User Administration - LDAP
Software version: 7.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 7.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 7.1, 188.8.131.52, 184.108.40.206
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 1326284
Modified date: 25 October 2009