RTC3.0 LDAP AD problem
I have had an issue authenticating with imported LDAP users after completing the jts/setup stage and copying over LDAP server.xml and web.xml files.
Logging on with an imported LDAP user gives an invalid user/password error, but I am still able to logon with tomcat user IDs even though the user registry type is now set to LDAP.
com.ibm.team.repository.user.registry.type=LDAP
Is there a step I am missing or anything I can check to find out why this is not working for me.
Thanks,
Kelly
Logging on with an imported LDAP user gives an invalid user/password error, but I am still able to logon with tomcat user IDs even though the user registry type is now set to LDAP.
com.ibm.team.repository.user.registry.type=LDAP
Is there a step I am missing or anything I can check to find out why this is not working for me.
Thanks,
Kelly
3 answers
I have had an issue authenticating with imported LDAP users after completing the jts/setup stage and copying over LDAP server.xml and web.xml files.
Logging on with an imported LDAP user gives an invalid user/password error, but I am still able to logon with tomcat user IDs even though the user registry type is now set to LDAP.
com.ibm.team.repository.user.registry.type=LDAP
Is there a step I am missing or anything I can check to find out why this is not working for me.
Thanks,
Kelly
Hi Kelly
Did you restart the RTC server after changing the LDAP settings (server.shutdown then server.startup)?
anthony
Hi Anthony,
yes I restarted the server after making the config changes and have also turned on LDAP DEBUG logging in both the jts and jazz logs, but can't log on using a valid LDAP account.
Interestingly, with the debug logging on I can see that I connect to our AD server successfully and am able to import users from our AD server successfully (while logged on using a tomcat admin ID) with the correct external registry mappings in place for JazzAdmins etc.,
yes I restarted the server after making the config changes and have also turned on LDAP DEBUG logging in both the jts and jazz logs, but can't log on using a valid LDAP account.
Interestingly, with the debug logging on I can see that I connect to our AD server successfully and am able to import users from our AD server successfully (while logged on using a tomcat admin ID) with the correct external registry mappings in place for JazzAdmins etc.,
Hi Anthony,
yes I restarted the server after making the config changes and have also turned on LDAP DEBUG logging in both the jts and jazz logs, but can't log on using a valid LDAP account.
Interestingly, with the debug logging on I can see that I connect to our AD server successfully and am able to import users from our AD server successfully (while logged on using a tomcat admin ID) with the correct external registry mappings in place for JazzAdmins etc.,
Is this the server you set up with Stu's silent-install response file - and using the /jazz context on a new database (rather than an upgrade of a 2.x repository)? We saw odd behaviour on another instance where a new installed used the /jazz context rather than /ccm.
anthony