Bug 782976

Summary: [RFE] SUDO: --users and --groups should detect values such as "ALL" and error appropriately
Product: Red Hat Enterprise Linux 6 Reporter: Dmitri Pal <dpal>
Component: ipaAssignee: Rob Crittenden <rcritten>
Status: CLOSED ERRATA QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: grajaiya, jgalipea, mkosek, nsoman, shaines
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-2.2.0-1.el6 Doc Type: Enhancement
Doc Text:
No documentation needed.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 13:30:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
test output none

Description Dmitri Pal 2012-01-19 00:31:19 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/1496

Setting --groups=ALL or --users=ALL with - sudorule-add-runasuser , and other special values that are allowed in the SUDOers configuration file should result in error.  These values are not supported in IPA sudo rules.
Comment 1 Martin Kosek 2012-01-19 09:45:00 UTC 
Fixed upstream:

master:4622812a4f41568ca0c77dbc5a2409dda8b843af
ipa-2-2: 3d532187e607e3264993cb2189353f55a6cb8f0c
Comment 5 Martin Kosek 2012-04-20 11:39:53 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.
Comment 6 Namita Soman 2012-05-11 12:48:22 UTC 
Created attachment 583834 [details]
test output

Verified using ipa-server.x86_64 0:2.2.0-13.el6
Attaching test output from beaker run
Comment 8 errata-xmlrpc 2012-06-20 13:30:15 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.

http://rhn.redhat.com/errata/RHBA-2012-0819.html