Bug 48623 - AuthLDAPURL syntax is not RFC-compliant, prevents common failover scenarios
Summary: AuthLDAPURL syntax is not RFC-compliant, prevents common failover scenarios
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_authz_ldap (show other bugs)
Version: 2.2.3
Hardware: All All
: P2 major (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2010-01-26 08:01 UTC by charlie
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description charlie 2010-01-26 08:01:52 UTC
mod_authnz_ldap documentation says the first parameter to the AuthLDAPURL directive is an RFC2255 LDAP URI (the current relevant RFCs are 4516 and 4510), but the method which has been used for host failover breaks RFC compliance.

My mod_authnz_ldap, which came bundled with Red Hat Enterprise Linux v5.4 as part of their httpd-2.2.3-31.el5_4.2 package, requires this for syntax:

transport://host host host host host:port/dn?filter-etc

this is not RFC compliant, you cannot embed multiple hosts like that. This is a
hack that prevents several commonplace LDAP failover usages.

This is the right way to do it:

transport://host:port/dn?filter-etc transport://host:port/dn?filter-etc

For example, in an arbitrarily complex two host failover setup:

AuthLDAPURL ldap://,dc=example,dc=edu?mailuid?one?objectclass=mailuser  ldaps://ldap.example.edu/ou=People,dc=example,dc=edu?uid?one?objectclass=posixAccount

(Note, buzilla's probably wrapping that, it should all be on one line.)

Any number of space-separated host specifications should be allowed, although three will be enough for most real-world use cases.

Since RFC-compliant strings may contain spaces internally, quoting of individual host specifications must be allowed.
Comment 1 Mark A. Ziesemer 2010-12-28 16:18:39 UTC
(This bug relates to previous discussion on bug 48505.)

Not to hijack this bug report, but please also review the almost 3-year-old bug 44302 relating to ldapi:/// URLs as part of this.
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:56 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.