Red Hat Bugzilla – Bug 880176
memberUid required for primary groups to match sudo rule
Last modified: 2013-02-21 04:41:17 EST
Description of problem: sudo rules with %group_name or %#group_id sudoUser don't match for primary groups not having user's memberUid. 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 Execute "su -c 'sudo -u user2 true' user1 && echo allowed || echo denied" as root. Actual results: denied Expected results: allowed Additional info: If the primary group (group_user1) has a memberUid with user name (user1) added, the above works as expected. This will still not work with sudoUser specified as group ID (i.e. %#20001), even with memberUid added, because of https://fedorahosted.org/sssd/ticket/1667.
This is branched off Bug 872619. Assigning to Pavel accordingly.
Created attachment 651937 [details] Base LDIF file
Created attachment 651938 [details] sssd.conf
Upstream ticket: https://fedorahosted.org/sssd/ticket/1677
Verified %group_name works with the following packages: sssd-1.9.2-45.el6.x86_64 sssd-client-1.9.2-45.el6.x86_64 sudo-1.8.6p3-6.el6.x86_64 libsss_idmap-1.9.2-45.el6.x86_64 libsss_sudo-1.9.2-45.el6.x86_64 Relevant sudo suite output: :: [ PASS ] :: attrs_user_group_name_match However, cannot verify %#group_id, because of Bug 880335.
(In reply to comment #7) > However, cannot verify %#group_id, because of Bug 880335. That bug is not going to get fixed until el7. If that's the only thing that doesn't work, please move to VERIFIED.
Once Bug 880335 is fixed, the sudo suite output relevant to %#group_id verification should change from: :: [ FAIL ] :: attrs_user_group_id_match (Expected 0, got 1) to: :: [ PASS ] :: attrs_user_group_id_match
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. http://rhn.redhat.com/errata/RHSA-2013-0508.html