RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

We have seen cases where it takes a long time (multiple seconds) for a user to login even though the cache has been populated with all the LDAP entries already.

Some work has been done upstream already to address this issue:
https://github.com/SSSD/sssd/pull/332

This BZ is to track all related customer cases.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

We already have https://bugzilla.redhat.com/show_bug.cgi?id=1482555 which is fully acked for 7.5 already. Would you prefer to mark this bug as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1482555 or the other way around?

(In reply to Jakub Hrozek from comment #2)
> We already have https://bugzilla.redhat.com/show_bug.cgi?id=1482555 which is
> fully acked for 7.5 already. Would you prefer to mark this bug as a
> duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1482555 or the
> other way around?

Ah, thank you. I will close this one as a DUP of 1482555 .

*** This bug has been marked as a duplicate of bug 1482555 ***