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 1278761 - add logging for wrong keys/values set in pam_ldap.conf
Summary: add logging for wrong keys/values set in pam_ldap.conf
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pam_ldap
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-06 11:13 UTC by Michele Casaburo
Modified: 2023-09-14 03:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-27 07:19:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michele Casaburo 2015-11-06 11:13:13 UTC
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

Comment 9 Red Hat Bugzilla 2023-09-14 03:12:40 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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