If you have to look up a number of LDAP objects where only the DN is know, think of a DN list in a member attribute, there exist an efficient way to look them up in a single run. This is called 'dereference control' (http://tools.ietf.org/html/draft-masarati-ldap-deref-00) or 'Attribute Scoped Queries (ASQ)' (http://msdn.microsoft.com/en-us/library/aa366976%28VS.85%29.aspx). The problem is, that there is no real standard. OpenLDAP and 389ds use the deference control, Active Directory server ASQ. Other LDAP server may use different ways.
It would be nice if a generic API can be created for sssd, e.g. sdap_deref_send/_recv(), which hides all the details of the different implentations and can fall back to a series of base searches if no other way is available on the server side.
There are already two TODOs is sdap_async_accounts.c:
/* TODO: test rootDSE for deref support and use it if available */ /* TODO: or test rootDSE for ASQ support and use it if available */
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.6.0
coverity: => milestone: SSSD 1.6.0 => SSSD Deferred upgrade: => 0
milestone: SSSD Deferred => NEEDS_TRIAGE patch: => 0
milestone: NEEDS_TRIAGE => SSSD 1.6.0 priority: major => blocker
owner: somebody => jhrozek
patch: 0 => 1 status: new => assigned
Fixed in master: d4bfba145e74aa8c0f9e7c36e548fc9965822a12
258d4b400f72e89f4428302d82c886f9c4c45c3e
2cc60b61c8d487221f88703b1784a92d9a1525e4
0a4b0580d8f5de1733ea065553992edfcb793de5
4dbc76b8784eed6dbf4d9b40c0f59fd0bceeeec7
resolution: => fixed status: assigned => closed
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=785872
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=785872 785872]
Metadata Update from @sbose: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.6.0
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/1677
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.