Bug 1108835

Summary:	Enabling LDAP on one RHQ Server in HA Configuration is not propagated to another server(s) until their restart so the users cannot log in
Product:	[Other] RHQ Project	Reporter:	bkramer <bkramer>
Component:	Core Server	Assignee:	Jay Shaughnessy <jshaughn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	hrupp
Target Milestone:	---
Target Release:	RHQ 4.12
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-15 11:36:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1108833

Description bkramer 2014-06-12 16:06:59 UTC

Description of problem:
Enabling LDAP on one RHQ Server in HA Configuration is not propagated to another server(s) until their restart so the users cannot log in

Version-Release number of selected component (if applicable):
RHQ 4.9.0 

How reproducible:
Always


Steps to Reproduce:
1. Install and configure RHQ server1;
2. Start server1;
3. Install and configure RHQ server2;
4. Start server2;
5. Confirm that everything works fine and that servers 1 and 2 are in HA mode;
6. Configure LDAP settings on server1;
7. Log out from RHQ UI and attempt to log in again using LDAP username/password;
8. Confirm that this worked fine;
9. Using the same username/password attempt to log in to the RHQ UI on the second server;


Actual results:
Log in to the second server will fail with the message "  The username or password provided does not match our records."

Expected results:
log in to the second server is successful.


Additional info:
If the server2 is restarted, the server will read the LDAP configuration and after this, the log in will work.

Comment 1 Heiko W. Rupp 2014-07-03 09:42:09 UTC

I think you already fixed that?

Comment 2 Jay Shaughnessy 2014-07-03 18:55:10 UTC

Yes, this is already in master from the JON 3.3 BZ for the same issue:

master commit cde3c29b8e0b12d838de52453e1a4dc9bfb59d34
Author: Jay Shaughnessy <jshaughn>
Date:   Tue Jul 1 21:12:21 2014 -0400

    Enable/Disable of LDAP requires a system reconfigure (reinstall the JAAS
    login modules...). Change things such that the system reconfigure gets
    performed whenever HA nodes detect a change in system settings. So,
    this fix is a bit more general that the specific case listed here.  The
    system settings update check is every 60s, so HA nodes should pick up
    a change within a minute.


The testing for this can be done against 4.12 or JON 3.3, up to QE I guess, or possibly this should be closed as a duplicate of Bug 1108833.

Comment 3 Heiko W. Rupp 2014-12-15 11:36:11 UTC

Bulk close of items fixed in RHQ 4.12

If you think this is not solved, then please open a *new* BZ and link to this one.