Hide Forgot
Description of problem: the ldap login integration no longer works. Version-Release number of selected component (if applicable): How reproducible: Every time. Steps to Reproduce: 1.Enable ldap integration 2.Attempt to login with a valid user/pass. 3. Actual results: Displays "The username or password provided does not match our records". Expected results: Logins with ldap creds should work. Additional info: This is a regression. This used to work. Using the TestLdapSettings tool the authentication and authorization works correctly with the current credentials.
Bounce the server and the ldap logins start working again. This looks to be because we do not trigger a reload of the JAAS login modules after saving LDAP settings. So not as bad as I initially thought.
Fixed with commit in master: b4aba0e75695b9b06beaa2e1ec84af07296fad2e
verified RHQ 4.0 CR1, as follows. I set up my own LDAP server according to the directions at this URL: http://www.rhq-project.org/display/RHQ/Testing+the+RHQ+LDAP+Integration I was able to edit the LDAP settings and they took without the need to bounce the RHQ server. Successfully logged in authenticating as an LDAP user I configured in my LDAP server.
Bookkeeping - closing bug - fixed in recent release.