Bug 119332

Summary:	mod_authz_ldap cannot bind to secondary LDAP server
Product:	Red Hat Enterprise Linux 3	Reporter:	Peter Lannigan <peter.lannigan>
Component:	mod_authz_ldap	Assignee:	Joe Orton <jorton>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 19:28:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Lannigan 2004-03-29 16:29:45 UTC

Description of problem:
It seems that mod_authz_ldap lacks any mechanism to specify more than
one LDAP server.  If that LDAP server goes down then all
authentication to the website fails.  This does not fit in an
"Enterprise Operating System".

Version-Release number of selected component (if applicable):
mod_authz_ldap-0.22-3

How reproducible:
Always. In the config AuthzLDAPServer takes only one argument.

Steps to Reproduce:
1.Load apache and mod_authz_ldap rpms for RHEL3
2.Configure AuthzLDAP* parameters
3.Shutoff your LDAP server -- you're hosed.
  
Actual results:


Expected results:


Additional info:

Comment 1 Joe Orton 2004-03-30 13:06:41 UTC

Thanks for reporting this.

Comment 2 RHEL Program Management 2007-10-19 19:28:22 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.