#2158 PAC responder needs much time to process large group lists
Closed: Fixed None Opened 7 years ago by steeve.

For example, when AD user is part of 500 groups

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => 0

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.12.1

The same mechanism could be reused when looking up IDs from token groups when ID mapping is off.

Fields changed

review: 0 => 1

Mass-moving all tickets that didn't make 1.12.1 into 1.12.2

milestone: SSSD 1.12.1 => SSSD 1.12.2

We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3

milestone: SSSD 1.12.2 => SSSD 1.12.3

Downstream no longer needs this enhancement in the next release. Moving to 1.13

mark: => 0
milestone: SSSD 1.12.3 => SSSD 1.13 beta

Sumit has a plan to process the PAC in the back end and make the PAC responder smaller. We really need this to happen in the next release.

priority: major => critical

Per out face-to-face meeting last weeks, this is a stretch goal for 1.13. Moving to 1.13 backlog for now.

milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: critical => major

Fields changed

priority: major => critical

Re-setting priority of 1.13 backlog tickets used for planning.

priority: critical => major

Fields changed

priority: major => critical
sensitive: => 0

Fields changed

owner: somebody => sbose
status: new => assigned

Sumit is working on this ticket at the moment, therefore it's 1.14 Alpha target

milestone: SSSD 1.13 backlog => SSSD 1.14 alpha

Fields changed

patch: 0 => 1

Metadata Update from @steeve:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.14 alpha

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

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.