Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The RFE is to request 'Location Dependent' DNS views with IdM's packaged DNS server.
With the default configuraton of DNS with IdM, each IdM server has SRV records that have the same priority/weight. In environments that span multiple physical sites, authentication requests are frequently serviced via an IdM server that is not 'local' to the client. Due to this, logging into applications who use IdM can be at times rather slow, depending on the behavior of the DNS client as well as the network connectivity between sites.
Example:
Assume the realm of example.com consists of three sites, sites A, B, & C respectively. (These sites could be representative of multiple datacenters, for example)
Site A
- Has IP Subnet of 192.168.0.0/24
- Has IdM server idm01.example.com
Site B
- Has IP Subnet of 192.168.1.0/24
- Has IdM server idm02.example.com
Site C
- Has IP Subnet of 192.168.2.0/24
- Has IdM server idm03.example.com
If one was to query DNS for each we'd get
$host -t srv _kerberos._udp.example.com
_kerberos._udp.example.com has SRV record 0 100 88 idm01.example.com.
_kerberos._udp.example.com has SRV record 0 100 88 idm02.example.com.
_kerberos._udp.example.com has SRV record 0 100 88 idm03.example.com.
What would be preferred is a mechanism for an administrator to define their 'DNS Topology', where they'd define the above relationship between their Sites, subnets, and the IdM systems within them. This would give the administrator the capability of saying 'clients in Site A prefer to use IdM servers in Site A'. This can then be implemented within IdM using bind views, to give a view of the zone with the most local IdM server carrying a lower priority/weight (and thus more preferred) than the others.
Conceptually, a close anology to this would be Active Directory Sites & Services (http://technet.microsoft.com/en-us/library/cc730868.aspx)