Bug 1278761 - add logging for wrong keys/values set in pam_ldap.conf [NEEDINFO]
add logging for wrong keys/values set in pam_ldap.conf
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pam_ldap (Show other bugs)
6.8
Unspecified Unspecified
unspecified Severity low
: rc
: ---
Assigned To: Jakub Hrozek
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-06 06:13 EST by Michele Casaburo
Modified: 2016-04-27 03:19 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-27 03:19:30 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
gagriogi: needinfo? (pgm-pbu-tools)


Attachments (Terms of Use)

  None (edit)
Description Michele Casaburo 2015-11-06 06:13:13 EST
Hi,
I think it might be useful adding logs if some keys/values set in pam_ldap.conf are wrong. 

Misspelling something is not difficult and having a feedback from the system for having discarded the non-existing key/value would be useful, above all considering that understanding what is the default value if the key is valid, but the value is not, is not always easy.

Just a simple real world example, one of our customers set:

pam_password = expo

and in spites having checked the conf file a few times, he did not spot the switch, hence opened a case with us.
And, I have to say, spotting the switch took a while to me as well...

I am opening it as a bug and not as RFE, because, well, in my opinion not providing any kind of feedbacks to the sysadmin can be considered a bug, but, obviously I can fill the required RFE template if you think otherwise. 

Please let me know how I can help

Michele
---
gss

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