steps to reproduce: * configure ldap authentication * enable ldap authentication * try to login using ldap user -- rhq uses ldap login module * reboot rhq server * try to login using ldap user -- rhq uses jdbc login module * login as rhqadmin * check settings -- ldap authentication is enabled in ui, but not in login logic -- deactivate ldap authentication & save changes -- reactivate ldap authentication & save * logout rhqadmin and login using ldap user -- rhq still uses jdbc login module * login as rhqadmin' -- go to settings and change e.g. login property to e.g. 'invalidattr' & save -- change back login property to the correct value e.g. 'uid' & save * logout rhqadmin and login using ldap user -- now rhq is using the ldap login module
Tested on jopr 2.2.0
i'll look at this
what kinds of error messages do you see in the server logs?
look at your server logs, it should say this (even when you reboot - this is the startup stuff) INFO [CustomJaasDeploymentService] Installing RHQ Server's JAAS login modules ... INFO [CustomJaasDeploymentService] Enabling RHQ LDAP JAAS Provider I have not been able to reproduce this. My LDAP is properly configured and it remains so even after a reboot. I log in as an LDAP user and it uses LDAP to authenticate the user. Look in your database, table RHQ_SYSTEM_CONFIG and check the LDAP settings - make sure they are your latest values -this ensures the database update to your settings was successful.
I'll need to know what the exact LDAP settings were in the Settings UI page, too that reproduced this error
lowering down to major priority until we can confirm this really is a problem in the new stuff. I tested on trunk/HEAD (soon to be released) and I was not able to see any problems with the LDAP login modules even after re-starting the server.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2066 This bug relates to RHQ-2189
simeon did alot of LDAP work recently. I suspect this is fixed. Assigning to him to look it over and move to ON_QA if appropriate.
This doesn't happen anymore. As long as the LDAP server is up the JAAS auth does enable successfully through reboots. Moving to ON_QA.
Verified in build 107 (Version: 4.1.0-SNAPSHOT Build Number: 9192306) Configured the ldap settings and logged in successfully with ldap user. Restarted RHQ server and verified that the ldap users are able to login successfully. Marking as verified.
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.