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
rhbz: => 0
Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Patches welcome
to comment on this ticket.
Copyright © 2014-2017 Red Hat
2.90.1 — Documentation