Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.7.0

If the benefit is high and the cost is low let us do it in 1.6.1. Otherwise we will bounce it back.

milestone: SSSD 1.8.0 => SSSD 1.6.1

The cost is not low. While it would reduce the amount of processing we do, it is not simple to accomplish, especially with nested groups.

Basically, we still have to descend into nested group processing to make sure that none of its parentage has changed, even if the object itself has.

There's gain to be had here, but I think the cost is too high for 1.6.1.

Returning to NEEDS_TRIAGE.

milestone: SSSD 1.6.1 => NEEDS_TRIAGE
rhbz: =>

Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

rhbz: => 0

This is essentially what we do already, except we use modifyTimestamp. Therefore I would suggest to close this bug in its current form and reopen if needed.

blockedby: =>
blocking: =>
changelog: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: => 0
review: => 1
selected: =>
sensitive: => 0

Fields changed

component: SSSD => LDAP Provider

Closing because we already optimize lookups using modifyTimestamp

resolution: => wontfix
status: new => closed

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

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.