Bug 48623 - AuthLDAPURL syntax is not RFC-compliant, prevents common failover scenarios
Summary: AuthLDAPURL syntax is not RFC-compliant, prevents common failover scenarios
Status: NEW
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
Depends on:
Reported: 2010-01-26 08:01 UTC by charlie
Modified: 2010-12-28 16:18 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.