Bug 1413160

What problem/issue/behavior are you having trouble with?  What do you expect to see?

1. Proposed title of this feature request
Sudo option to quietly ignore unknown defaults settings

3. What is the nature and description of the request? 
Customer is making use of sudo in LDAP.
In LDAP they have to configure a number of parameters, like netgroup_tuple.
This option is unknown i.e. in sudo for RHEL 5 and therefore an error is printed in the output.
ie: "sudo: unknown defaults entry [...]"

This is breaking some scripts and programs, especially when output is checked.

4. Why does the customer need this? (List the business requirements here)
Customer needs to be sure that next option introduced will not affect current existing running environment.

5. How would the customer like to achieve this? (List the functional requirements here)
Add option in sudo like:
```
Defaults quiet_unknown_options="netgroup_tuple,env_reset"
```
ALL may be a special wording to quietly ignore the unknown options.

6. For each functional requirement listed in question 5, specify how Red Hat
and the customer can test to confirm the requirement is successfully implemented.
Add in sudoers:
```
Defaults testoption1
Defaults testoption2
```

run sudo -l and check the output.
"sudo: unknown defaults entry" string should appear for testoption1 and testoption2.

Add now in sudoers:
```
Defaults quiet_unknown_options="testoption1"
```

run sudo -l and check the output.
"sudo: unknown defaults entry" should appear only for testoption2

Edit the above with:
```
Defaults quiet_unknown_options="testoption1,testoption2"
```
run sudo -l and check the output.
No string should appear at all.

Edit the above with:
```
Defaults quiet_unknown_options="ALL"
```
run sudo -l and check the output.
No string should appear at all.

8. Does the customer have any specific timeline dependencies?
End of Q1 of 2017

9. Is the sales team involved in this request and do they have any additional input?
no 

11. Would the customer be able to assist in testing this functionality if implemented?
Yes, sure

Where are you experiencing the behavior?  What environment?

RFE

When does the behavior occur? Frequently?  Repeatedly?   At certain times?

RFE

What information can you provide around timeframes and urgency?

RFE