Bug 1053030 - [RFE][AAA] Mechanism for determining which Domain Controller is 'active' for authentication
Summary: [RFE][AAA] Mechanism for determining which Domain Controller is 'active' for ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.2.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 3.5.0
Assignee: Scott Herold
QA Contact: Shai Revivo
URL:
Whiteboard: infra
Depends On:
Blocks: oVirt-AAA-LDAP
TreeView+ depends on / blocked
 
Reported: 2014-01-14 15:37 UTC by Clifton Coursey
Modified: 2019-08-15 03:45 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-21 12:07:07 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:
sherold: Triaged+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 530583 0 None None None Never

Description Clifton Coursey 2014-01-14 15:37:28 UTC
Description of problem:
How can we determine what domain controller is currently being used for Active Directory Authentication and other AD requests?

We will be implementing the multiple Domain Controller
This capability  will be required in order to troubleshoot possible  future AD authentication issues.
Addition we would like to know what the Failover mechanism is? 

For example:
If we have 3 domain controllers listed how does rhevm determine which AD controller is used to service requests and what is the critera that us used to failover to the next one.


Version-Release number of selected component (if applicable):
N/A

How reproducible:
N/A


Additional info:
The only way to get an idea of this information is the following:
Do a service record lookup...

# dig -t SRV _ldap._tcp.yourdomain.com

Comment 6 Alon Bar-Lev 2015-02-03 11:28:32 UTC
in 3.5 using the new LDAP provider ovirt-engine-extension-aaa-ldap[1][2], there are several policies (serverset) to access domain.

the recommendation for active directory is to use DNS SRVRecord, which will select the server with the higher priority and refresh every interval.

you can select other policies if you like.

enabling debug at level ALL will also enable you to see what ip address is being accessed.

[1] http://gerrit.ovirt.org/gitweb?p=ovirt-engine-extension-aaa-ldap.git;a=blob;f=README;hb=HEAD
[2] http://gerrit.ovirt.org/gitweb?p=ovirt-engine-extension-aaa-ldap.git;a=blob;f=README.profile;hb=HEAD


Note You need to log in before you can comment on or make changes to this bug.