#1062 lookup parent groups during RFC2307bis initgroups in parallel
Closed: wontfix 4 years ago by pbrezina. Opened 12 years ago by jhrozek.

For users who are members of large and complex group memberships, looking up all the groups can be time consuming. We are searching for the groups sequentially -- the reason we coded inigroups sequentially was that we were trying to avoid the trouble of having to detect loops in inter-group memberships.

We should reconsider looking up the groups (at least for one nesting level) in parallel. The loop problem should be solved by storing the groups in a hash, which we do already and checking if a group was already processed.


How many concurrent requests the server supports? We need to have this feature configurable.

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

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

4 years ago

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

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.

Login to comment on this ticket.

Metadata