CLM 5.0.2 with Websphere and Edirectory switching to Active Directory
![]()
Our company is discontinuing the use of eDirectory so all application must migrate to AD.
Since both WAS and CLM have LDAP connection information and user group / role definitions, I am trying to figure out the sequence of how changes can be made and if I run the risk of locking out my environment if they are not done 100% correctly the first time. Do we change Websphere to AD including the security role to user / group mapping first? After the JVM restart, can I log in to CLM still if WAS has been "flipped to AD" but CLM still has the eDirectory configurations? If so, then I am fine and I can "fix" JTS and RTC as long as it still thinks I'm an admin. Or do I try to change the LDAP settings in CLM first and then do the websphere changes and hope that after the JVM restart, everything still works with the new settings? Someone must have done this. Interested in the tricks to minimize the pain. Thanks! |
Accepted answer
![]()
To switch to another LDAP server, first you need to keep the Jazz user Id same as the previous.
The procedure will be:
1. On AD, create the LDAP users which have the same user id and Jazz groups as the old LDAP server.
2. Change the LDAP configuration to point to the new AD server in WAS
3. Redo the group mapping for all applications in WAS
4. Login jts/admin and modify the LDAP configuration. Or you can modify the configuration by manually update conf/jts/teamserver.properties.
Hope the above is helpful.
Ralph Schoon selected this answer as the correct answer
|
One other answer
![]()
For your concerns, all it matters is the LDAP configuration in WAS. You will need correct LDAP server configuration in WAS so that your credential is accepted. You will need correct security role mapping for each CLM application to identify yourself as an "admin" (as having the JazzAdmins role). You can always fix the LDAP configuration in JTS later down the track, as it's for user synchronization only, not for authentication.
Comments Thanks to both of you for responding. We were successful in cutting over to AD in our Dev/test environment. However, I am seeing some odd issues with case of the IDs.
Once we are able to eliminated the case insensitve duplicate users by changing some of the IDs using this method (which we have working) https://rsjazz.wordpress.com/2012/10/12/changing-the-jazz-user-id-using-the-rtc-plain-java-client-libraries/
|
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.