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.

Bug 880335

Summary: sudoUser %#group_id values not supported
Product: Red Hat Enterprise Linux 7 Reporter: Nikolai Kondrashov <nikolai.kondrashov>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED UPSTREAM QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: grajaiya, jgalipea, jhrozek, pbrezina
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 09:39:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Base LDIF file
none
sssd.conf none

Description Nikolai Kondrashov 2012-11-26 18:14:24 UTC
Description of problem:
%#group_id values of sudoUser attribute are not supported - sudo rules with these values never match

Version-Release number of selected component (if applicable):
libsss_autofs-1.9.2-21.el6.x86_64
libsss_idmap-1.9.2-21.el6.x86_64
sssd-1.9.2-21.el6.x86_64
sssd-client-1.9.2-21.el6.x86_64
libsss_sudo-1.9.2-21.el6.x86_64
sudo-1.8.6p3-5.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Use attached LDIF file to fill LDAP directory.
2. Use attached sssd.conf as the base for client configuration.
3. Execute "su -c 'sudo -u user2 true' user1 && echo allowed || echo denied" as root.
  
Actual results:
denied

Expected results:
allowed

Additional info:
The attached LDIF file has memberUid attribute explicitly referring to the primary group's (group_user1) user (user1) to workaround Bug 880176.

The bare LDAP sudo backend works with this.

Trac ticket: https://fedorahosted.org/sssd/ticket/1667

Comment 1 Nikolai Kondrashov 2012-11-26 18:15:07 UTC
Created attachment 652147 [details]
Base LDIF file

Comment 2 Nikolai Kondrashov 2012-11-26 18:15:45 UTC
Created attachment 652148 [details]
sssd.conf

Comment 3 Nikolai Kondrashov 2012-11-26 18:16:50 UTC
This bug is branched off Bug 872619. Assigning to Pavel accordingly.

Comment 5 Jakub Hrozek 2012-11-29 08:11:09 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/1678

Comment 7 Jakub Hrozek 2016-11-23 14:15:35 UTC
Thank you for filing this bug report.

Since fixing this bug requires work in the upstream SSSD project which is not scheduled for the immediate future, I added a conditional development nack, pending upstream availability.

Comment 8 Jakub Hrozek 2017-08-08 09:39:18 UTC
Thank you for filing the bug.

Since the bug was filed about 5 years ago and since then there was nobody hit by this issue, I think it's fine to keep tracking the bug in upstream only.

Therefore, I'm closing the bug with the resolution UPSTREAM.