Bug 782644

Summary:	Simple LDAP Authentication does not appear to work in RHEL4
Product:	Red Hat Enterprise Linux 4	Reporter:	Jason Breitman <jasonbreitman>
Component:	autofs5	Assignee:	Ian Kent <ikent>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	jmoyer
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 13:33:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jason Breitman 2012-01-18 02:40:41 UTC

Description of problem:
/etc/autofs_ldap_auth.conf does not appear to allow
authrequired=simple
Ian Kent made a patch for me in RHEL5 and the fix is now in the standard rpm on RHEL5 and RHEL6 to allow simple ldap authentication.


Version-Release number of selected component (if applicable):
#  rpm -q autofs5
autofs5-5.0.1-0.rc2.114

How reproducible:
It is easy to see.

Steps to Reproduce:
1. yum install autofs5
2. point /etc/auto.master to an ldap map 
3. configure /etc/nsswitch.conf to use ldap for automount.
4. configure /etc/autofs_ldap_auth.conf with ldap credentials
5. configure /etc/sysconfig/autofs5 with ldap servers, base and schema. 
6. restart automount
  
Actual results:
automount[9027]: parse_ldap_config: lookup(ldap): The authrequired property must have value "yes", "no" or "autodetect".

Expected results:
Successful moount of home directory.

Additional info:

Comment 1 Jiri Pallich 2012-06-20 13:33:03 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.