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.

Created attachment 1748800 [details]
sssd- debugging showing the

Description of problem:
Removing a secondary group from a local user, sssd continues to show that user in the secondary group using the 'id' command even after the group has been removed. The local user does not show up in that group using the 'getent group' command. 

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

How reproducible:
Everytime

Steps to Reproduce:
1. Remove user from testgroup:
     - # gpasswd -d test1 testgroup
2. Test that user is not in secondary group:
     - # groups test1
       test1 : users testgroup
3. Wait until the next morning:
     - # date; groups test1
       test1 : users testgroup

Actual results:
User is still showing as a part of the removed secondary group

Expected results:
User should be removed from the secondary group

Additional info:
- We have attempted to use the workaround/fix from https://bugzilla.redhat.com/show_bug.cgi?id=1886661
     - The customer said using "entry_cache_timeout" in the sssd.conf file did not help at all.

Thorsten suggested opening this as a Bugzilla, so I am.

Hi,

I think this is a duplicate of bz 1827432.

Could you please try 8.3 SSSD package (i.e. sssd-2.3.0-3.el8 or later)?

Hi,

The customer has tested this issue with the updated sssd packages and is still seeing this issue. I have provided the logs to the Bug.

Let me know if there is anything else needed from us at this time.

Corey Brown

Pull request: https://github.com/SSSD/sssd/pull/5784

Pushed PR: https://github.com/SSSD/sssd/pull/5784

* `master`
    * 301659a662a7a7aac11096fd0409f83b45cb41d1 - proxy: allow removing group members

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (sssd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2070