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.
Bug 1298975 - [RFE] Backport the groups merging feature
Summary: [RFE] Backport the groups merging feature
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Martin Sebor
QA Contact: Sergey Kolosov
Vladimír Slávik
URL:
Whiteboard:
: 1204503 (view as bug list)
Depends On:
Blocks: 1292074 1298243 1390370
TreeView+ depends on / blocked
 
Reported: 2016-01-15 15:06 UTC by Jakub Hrozek
Modified: 2020-09-10 09:30 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
*glibc* now supports group merging The ability to merge group members from different Name Service modules has been added to *glibc*. As a result, management of centralized user access control and group membership across multiple hosts is now easier.
Clone Of:
Environment:
Last Closed: 2017-08-01 18:06:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1463692 0 unspecified CLOSED glibc: Incorrect pointer alignment in NSS group merge result construction 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2017:1916 0 normal SHIPPED_LIVE Moderate: glibc security, bug fix, and enhancement update 2017-08-01 18:05:43 UTC
Sourceware 19072 0 P2 NEW Support for Group Merging 2021-01-27 12:13:22 UTC

Internal Links: 1463692

Description Jakub Hrozek 2016-01-15 15:06:51 UTC
Description of problem:
Upstream libc recently gained the possibility to merge group members from different Name Service modules. We should backport this feature to RHEL.

This would mainly enable deployments that depend on centralized directories to define members of well-known local groups (like wheel) in the centralized directory in addition to local files

Version-Release number of selected component (if applicable):
Whatever will be in RHEL-7.3

How reproducible:
always

Steps to Reproduce
1. set "group: files [SUCCESS=merge] sss" in nsswitch.con
2. define a group wheel in IPA or AD
3. getgrnam(wheel)

Actual results:
only local members are returned

Expected results:
getgrnam returns both members of the local wheel group as well as the members defined in the remote directory are returned


Additional info:
The related upstream bugzilla is https://sourceware.org/bugzilla/show_bug.cgi?id=19072

Comment 1 Jakub Hrozek 2016-01-15 15:08:26 UTC
Cockpit would also benefit from this feature.

Comment 3 Florian Weimer 2016-01-26 14:42:28 UTC
*** Bug 1204503 has been marked as a duplicate of this bug. ***

Comment 4 Florian Weimer 2016-01-26 14:43:51 UTC
To clarify, the patch has not been accepted yet upstream.

Comment 25 errata-xmlrpc 2017-08-01 18:06:55 UTC
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


Note You need to log in before you can comment on or make changes to this bug.