Not all AD servers are Global Catalog servers. So the address resolution for the Global Catalog need to be independent from the special 'ad port' trick, as the AD server we use for Krb/LDAP is not necessarily the same we want to use as Global Catalog.
The local 'Site' should be used in preference for the Global Catalog as well.

Related to #364

milestone: NEEDS_TRIAGE => SSSD 1.10 beta
rhbz: => 0
summary: Use the Global Catalog in SSSD for the AD provider => [RFE] Use the Global Catalog in SSSD for the AD provider

Fields changed

priority: major => critical

Fields changed

design: =>
design_review: => 0
fedora_test_page: =>
selected: => Want

Fields changed

design: => https://fedorahosted.org/sssd/wiki/DesignDocs/GlobalCatalogLookups
owner: somebody => sbose

Fields changed

review: => 0

Fields changed

owner: sbose => jhrozek
status: new => assigned

Fields changed

patch: 0 => 1

Fields changed

changelog: => Currently SSSD uses the standard LDAP interface of Active Directory to lookup users and groups when joined to an Active Directory domain. But the LDAP interface only offers information for users and groups of the local domain and not from the whole forest. This information is available in the Global Catalog of an Active Directory domain.
To make lookups of users and groups from the whole forest easier SSSD should use the Global Catalog instead of the standard LDAP interface for the lookups.

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=969883 (Red Hat Enterprise Linux 7)

rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=969883 969883]

• master:
  • 5546876b121d674077e93fe908f3a602de8ec31f
  • 55d80b1301fe969fb4ba2b9481027887b9462dbb
  • d27d7f2c270b69d0805633c4bedcf6d806acd5cd
  • a79c0a639c4ab26eacbc29f9f42bc95421e33f6e
  • 3ca846cfb59dee6e20b94c4aee2716f1a20ebd3a
  • 556040eac686265f8a3b20e2a744210607cba95c
  • 02d1cb8935d5c9b57cd05dfdbfe6ed38e0d61c28
  • c51f7a064b0d7ef86110bdeb6dc09fa6c08be7d3
  • ca344fdecdf127c80ad1074047aeba21e1165313
  • 749cfb5d3270b5daf389d51a0dbd3fd2aec6e05d
  • 9aa117a93e315f790a1922d9ac7bd484878b621e
  • e6e129a40e69af52a12deed91f68fff3569c51ce
  • dcb44c39dda9699cdd6488fd116a51ced0687de3
  • 7119f0c483049a8850d3075c0b1062f35200a538

resolution: => fixed
status: assigned => closed

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1042848 (Red Hat Enterprise Linux 6)

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=969883 969883] => [https://bugzilla.redhat.com/show_bug.cgi?id=969883 969883], [https://bugzilla.redhat.com/show_bug.cgi?id=1042848 1042848]

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/2599

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.