SSSD / sssd

#3409 Optimize IPA-specific LDAP searches to improve performance
Closed: duplicate by pbrezina. Opened by jhrozek.

Closed: duplicate
Reopen Issue

389-DS builds 'candidate lists' of potential matches from 'left-to-right', so it makes sense for the first component of the LDAP search to be the most specific.

Bad:
"(&(objectClass=ipaOverrideAnchor)(ipaAnchorUUID=:SID:S-XYZ-ABC))"

Good:
"(&(ipaAnchorUUID=:SID:S-XYZ-ABC)(objectClass=ipaOverrideAnchor))"

Note that this optimization only makes sense for 389-DS as we have no idea what other LDAP servers might be doing.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

Duplicate of https://pagure.io/SSSD/sssd/issue/3764.

Metadata Update from @pbrezina:
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

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

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.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.