#1366 [RFE] Optimize RFC2307bis lookups when user and group search bases do not overlap
Closed: Fixed None Opened 6 years ago by sgallagh.

One of the biggest performance issues with RFC2307bis servers is that, because a member attribute provides only a DN, we have to perform a lookup for that DN to determine if it is a user or a group.

One way we could optimize this and save ourselves some lookups would be to compare the DN to the set of configured search bases if (and only if) the user and group search bases do not overlap.

This check should be done once at startup time and saved in the ldap_id_ctx. It should only be done if the ldap_user_search_base and ldap_group_search_base are both populated during initialization (in other words, if we are autodetecting the search base from the RootDSE, don't bother doing this comparison then).


Note about multiple search bases: we need to make sure that no overlap exists across ANY of the multiple search bases. If overlap exists anywhere, disable this feature.

Fields changed

type: defect => enhancement

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.0
priority: major => critical

Fields changed

milestone: SSSD 1.10.0 => SSSD 1.11.0 (LTM)

Fields changed

proposed_priority: => Nice to have

Moving all the features planned for 1.10 release into 1.10 beta.

milestone: SSSD 1.11.0 (LTM) => SSSD 1.10 beta

Fields changed

owner: somebody => mzidek

Fields changed

design: =>
design_review: => 0
fedora_test_page: =>
summary: Optimize RFC2307bis lookups when user and group search bases do not overlap => [RFE] Optimize RFC2307bis lookups when user and group search bases do not overlap

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

This ticket already done as a result of earlier internal refactoring.

changelog: =>
milestone: SSSD 1.12 beta => Interim Bucket
priority: critical => major
review: => 0

Fields changed

milestone: Interim Bucket => SSSD 1.12 beta

Closing as this ticket has already been addressed as a part of major refactoring.

resolution: => fixed
status: new => closed

Fields changed

changelog: => N/A this enhancement was already addressed in 1.10.

Metadata Update from @sgallagh:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.12 beta

2 years ago

Login to comment on this ticket.

Metadata