Highlighted
Anthony Bachrac Absent Member.
Absent Member.
738 views

Enabling LDAP authentication

Jump to solution
We have been tasked with enabling LDAP authentication for user logon. Problem is we have had Quality Center up and running for three years now. Is there a method for updating user names to match their network id's?
Tags (1)
0 Likes
1 Solution

Accepted Solutions
Absent Member.. John Trent Absent Member..
Absent Member..

Re: Enabling LDAP authentication

Jump to solution
I suspose it is technically possible to physically change all of your user names in the database to their NT user ID equillivants. Not sure why you would want to do that. We didn't do anything when we transitioned to LDAP. Your users will continue to receive email notifications as long as the addresses didn't change. So it wasn't a big issue for us. Keep in mind when you change to LDAP, none of the old logins will work, so it is all or nothing. Good Luck!
5 Replies
Absent Member.. John Trent Absent Member..
Absent Member..

Re: Enabling LDAP authentication

Jump to solution
I suspose it is technically possible to physically change all of your user names in the database to their NT user ID equillivants. Not sure why you would want to do that. We didn't do anything when we transitioned to LDAP. Your users will continue to receive email notifications as long as the addresses didn't change. So it wasn't a big issue for us. Keep in mind when you change to LDAP, none of the old logins will work, so it is all or nothing. Good Luck!
Anthony Bachrac Absent Member.
Absent Member.

Re: Enabling LDAP authentication

Jump to solution
John, first off, thank you for the reply, it is greatly appreciated. One more question, were there any issues with user not being able to access previously created defects, test scripts, etc.?
0 Likes
Charles Seal
New Member.

Re: Enabling LDAP authentication

Jump to solution
We recently ran into a simliar dilemma. We've used QC for a few months and started importing LDAP users and enabled LDAP authentication. The problem we ran into was the USERS and the BUG tables for existing project. The data in those tables were the old QC user names. In addition, we were challenged with listing the person's FULLNAME instead of the User names (LDAP IDâ s) in the defect details.

To do this we had to create two new fields in the defect window that would contain the FULLNAME of the user who performed X action. (done using VB script) We also needed to update the old user information in the USERS and the BUG tables to replace the old data with the new LDAP ID's. This was done using a bunch of "update" SQL statements. As far as I know that is the only way for updating user names in QC to match their LDAP ID's. Hope this helps.
Anthony Bachrac Absent Member.
Absent Member.

Re: Enabling LDAP authentication

Jump to solution
Did you update the username in the system admin section, or just create new ones?
0 Likes
cwelch Absent Member.
Absent Member.

Re: Enabling LDAP authentication

Jump to solution
We hit the same problem. The compromise we used was to import the users from LDAP then copy the LDAP search string into their existing QC account.

This allows our users to keep their existing QC user ids, but with their LDAP password.

Only three users have the same uid in LDAP as they did in QC so most people here work this way.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.