Unable to import users after non-LDAP to LDAP switch in CLM 6.0.2
Hello
I've just upgraded from CLM 4.0.6 to CLM 6.0.2. By now we've used tomcat users for authentication. Now i want to change from tomcat users to LDAP (MS AD) authentication.
After the upgrade I ran the setup of JTS (https://myserver.com/jts/setup) then switched to LDAP authentication, configured ldap, and the test was successful. I saved the configuration and followed the steps to replace web.xml in the applications and server.xml in the tomcat/conf directory.
I restarted the server and noted that i can't login with my old credentials. I tried my AD credentials and the login worked fine (Note: the usernames of the tomcat user registry are the same as in AD).
However if i have a look under https://myserver.com/jts/admin#action=com.ibm.team.repository.admin.configureAdvanced all the LDAP related configurations have the default - non-LDAP - values. If i start the setup again, there ist still tomcat user registry selected, an my LDAP settings are note displayed.
If i want to import a user, none of the users in my AD groups are found.
Long story short, i can login with AD credentials for existing users where the username of the tomcat user registry matches the username in AD, but I cannot add new users from AD.
Did i miss someting? Do i need to configure some settings under Advanced Configuration? If yes which one?
Does someone have a complete guide how to switch from tomcat user registry to AD?
Thank you very much in advance.
Willi
2 answers
On the setup page where you set LDAP, there is a help link that guides you to an article that helps you to validate your LDAP settings. It looks like your LDAP parameters might be wrong.
I think we used AD in Rational solution for Collaborative Lifecycle Management 2012 Administration Workshop so maybe that is a little help. Note, I think we have an error there and the user ID attribute is wrong, but nevertheless....
I think we used AD in Rational solution for Collaborative Lifecycle Management 2012 Administration Workshop so maybe that is a little help. Note, I think we have an error there and the user ID attribute is wrong, but nevertheless....
Comments
There are two parts of the LDAP configuration - one for authentication and the other for user synchronization/import. When you run /jts/setup, the LDAP configuration should be recorded for the latter (in Advanced Properties/teamserver.properties). The content that you copied in tomcat/conf/server.xml deals with the former, which appears to be done correctly already. I'm not sure what's wrong with the setup process that the configuration did not get retained.
Comments
Will Girard
Sep 01 '16, 2:50 a.m.