How can users LDAP-imported user data be updated? (email ids)
Rational Team Concert 5.0.2
Linux How can user LDAP-imported user data be updated? A while back, our corporate email address domain changed from domainA to DomainB. Although either domain works now, eventually the original (DomainA) will go away. There are hundreds of older users of CLM whose email address domains are still set to the old domain (DomainA) despite the corresponding LDAP entry correctly set to the new domain (DomainB). We attempted to use the LDAP sync link on the JTS Server page which reported successful execution, but it did not update the email addresses. It is called: "Synchronize Jazz Team Server Users With External User Registry" and links to: https://clm.DomainA.com/jts/admin# We also tried "repotools-jts –syncUsers" the repository tools command to sync users with the LDAP users directory. It provided some updates for 14 (out of 855 needing email address changes), but only two with email address updates. We waited 30 more minutes for any updates, but nothing further. Is there a way to re-import user data or any way to update the imported user email addresses, which are currently not editable being linked to LDAP? |
One answer
Hello Daniel,
My experiance over the last few years with the LDAP synch below: - There is a big limitation with Jazz. JTS can only hold one set of LDAP configuration and so it can only import/update (synch) users, either manual or automatic with the defined LDAP registry (Advanced Properties). If your domains are all on one LDAP registry, be sure the LDAP search base is set on a common level, where both domains can be seen. - Generally my experience is, the LDAP synch is not the most stable application with JTS. We often saw such issues. Specially we never really where sure what will be synched when. The scheduled synch (defined in advanced properties) worked quite well. But the manual synch with the button, or the synch started with repotool were quite suspect. My recommendation, do the import/update by yourself, based on
- You write directly into the DB. - The LDAP settings in advanced properties are just ignored.
- If a userId does not exist, the record is created.
- If a userId exists, the record is updated (Name and email) - You can provide any value for name/id/email. This means you can set e.g. the name to a value combined out of different LDAP attributes. e.g. "givenname, surname, phone, department, location" - You can automatically archive users based on the disable flag on LDAP
So best is having a script, which reads out the LDAP groups from both domain, prepare a create/update file and a archive file and run repotools. This you can schedule with the OS scheduler or the RTC build system.
regards Guido
An example of a small cmd file:
set userID=admin.user@clmtest01.local
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.