It must be possible to determine the ClearQuest user name from the WebSphere Application Server-authenticated user name. If the ClearQuest user name and the WebSphere Application Server-authenticated user name do not match, then you must configure the LDAP mapping so that the ClearQuest user name can be derived at runtime.
Use LDAP mapping to determine the ClearQuest user by referencing a different user field than the logon name. For example, the user name of the WebSphere Application Server-authenticated user might be the employee ID, while the ClearQuest user name might be a more conventional logon name. By configuring LDAP mapping, the ClearQuest application can perform a look up by the employee ID saved in the Description field of the user record. See Setting up LDAP authentication for instructions on configuring a ClearQuest database for LDAP.
The following sequence of installutil subcommands configure a ClearQuest database set for LDAP mapping. The uid attribute in the LDAP directory stores the user names. The installutil setcqldapmap subcommand identifies CQ_LOGIN_NAME as the ClearQuest user profile mapping field. In place of an LDAP mapping attribute, the subcommand uses %login%, which resolves to the Rational ClearQuest logon name. See the Related reference section below for information on using the installutil subcommands.
installutil setauthenticationalgorithm 7.1.2 admin adminPW CQ_ONLY installutil setldapinit 7.1.2 admin adminPW "-h ourldapserver.ourcompany.com" installutil setldapsearch 7.1.2 admin adminPW "-s sub -b ou=my_dept, dc=ourcompany,dc=com (&(objectclass=inetOrgPerson)(uid=%login%))" installutil setcqldapmap 7.1.2 admin adminPW CQ_LOGIN_NAME %login% installutil validateldap 7.1.2 admin adminPW test_user testPW installutil setauthenticationalgorithm 7.1.2 admin adminPW CQ_FIRST