[Date Prev][Date Next] [Chronological] [Thread] [Top]

backend overlays

The proof-of-concept in CVS HEAD is now working. I haven't thought too hard
about how it interacts with backglue yet, that could be ugly. Probably the
two should be merged.

I've added a chaining wrapper to back-ldap as well. configure like so:

database bdb
suffix dc=example,dc=com
rootdn dc=example,dc=com
rootpw secret
overlay chain
uri ldap://subserver/
binddn o=foo,dc=example,dc=com
bindpw secret

The chaining code only takes effect if an operation on the backend gets an
LDAP_REFERRAL result. For Binds, the request is forwarded on a new connection
to the target server and if it succeeds, then the local connection is
authenticated. For other operations, the request is forwarded on a privileged
connection, using the Proxy Authorization control.

The idea behind chaining is to support a cluster of trusted servers that
collectively contain a DIT. The current implementation only supports one
referral target, since back-ldap currently only handles one URI per backend
instance. There's a bit of extending still needed to make this really useful.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support