Red Hat Bugzilla – Bug 974148
RHEV-M AD authentication does not work if one of the DCs is defunct.
Last modified: 2016-02-10 14:28:58 EST
Description of problem:
The admin portal is not able to authenticate the users from an Active Directory if one of the domain controllers is not reachable.
The registration and validation of the domain is Ok.
Version-Release number of selected component (if applicable):
100% in a specific configuration
Steps to Reproduce:
1. Register the RHEV-M to AD with two DCs
2. Turn off one of the DCs
3. Try to log in
The user is not allowed to log in.
The user is allowed to log in.
The bug has already been partially resolved upstream. The only remaining error was in root DSE query code block: when the first LDAP server in list was not available, there was an uncaught RuntimeException that prevents querying next LDAP server and makes login unsuccessful at once.
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.