Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Machines joined to a realm are not able to resolve centrally managed supplementary groups
Installing an Identity Management (IdM) server or client does not add the `sss` option to the `initgroups` lookup entry in the `/etc/nsswitch.conf` file. As a consequence, looking up secondary groups for users managed by SSSD does not work as expected. As a work around, remove or comment out the line starting with `initgroups` in the `/etc/nsswitch.conf` file before the installation. This ensures that machines joined to the realm resolve centrally managed supplementary groups as expected.
This is a complex issue and probably a minor regression caused by fix for bug 1329508.
Authconfig when writing nsswitch.conf actually comments out the initgroups entry because just placing the sssd into it modifies the behaviour (or at least that was originally the case) that was expected by users and applications (see bug 751450).
So I believe proper fix for this bug is to comment out the initgroups entry in default nsswitch.conf configuration.
There is no fix for this problem in authconfig apart from reverting the fix for bug 1329508 - however I do not think this is a proper solution.
Setting priority and severity to high/high.
In my opinion, this bug should be fixed in 7.3, because otherwise a domain member is not able to resolve supplementary groups, which is really a basic functionality.
Whether the fix comes in libc by removing the default initgroups line or in authconfig by changing the way nsswith.conf is generated is a detail from my point of view. But the case of installing a system and joining it to a domain with ipa-client-install is something we must fix.
BTW what will be a difference from glibc point of view between "removing default initgroups line" and adding sss to initgroups by default. "sss" is already a default for passwd and groups. But I know that initgrous is a little bit special case.
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, 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/RHSA-2017:1916