The SSSD IPA back end should be able to read special DNS entries that indicate which server is the closest one.
http://www.freeipa.org/page/DNS_Location_Discovery
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.6.0
coverity: => milestone: SSSD 1.6.0 => SSSD 2.0 upgrade: => 0
rhbz: => 0
This ticket is related to the DNS discovery and prioritization of the servers as well as DNS sites referenced in a different ticket. It can be fixed differently now.
blockedby: => blocking: => feature_milestone: => milestone: SSSD 2.0 => Temp milestone patch: => 0 proposed_priority: => Core
rhbz: 0 => todo summary: Add logic to connect to the closest server => [RFE] Add logic to connect to the closest server
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: Temp milestone => SSSD 1.10 beta
priority: major => critical
design: => design_review: => 0 fedora_test_page: => selected: => May
priority: critical => major
milestone: SSSD 1.10 beta => SSSD 1.11 beta review: => 0
mark: => 0
changelog: => owner: somebody => preichl
I think this was actually implemented, see src/providers/ipa/ipa_srv.c
Bumping to NEEDS_TRIAGE for discussion.
milestone: SSSD 1.13 beta => NEEDS_TRIAGE
The SSSD part is done.
resolution: => fixed status: new => closed
rhbz: todo => 0
Metadata Update from @dpal: - Issue assigned to preichl - Issue set to the milestone: NEEDS_TRIAGE
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1599
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.