Bug 119332 - mod_authz_ldap cannot bind to secondary LDAP server
Summary: mod_authz_ldap cannot bind to secondary LDAP server
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mod_authz_ldap
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Joe Orton
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-29 16:29 UTC by Peter Lannigan
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 19:28:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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