[Date Prev][Date Next]
RE: Can I reuse the back-ldap in my own overlay?
- To: "Chen, Shi Jun SLC CT PEK" <email@example.com>
- Subject: RE: Can I reuse the back-ldap in my own overlay?
- From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Date: Tue, 04 Jul 2006 22:48:38 -0700
- Cc: "Howard Chu" <firstname.lastname@example.org>, <openldap-software@OpenLDAP.org>
- In-reply-to: <DFBD1C5904D9E647868651D5C6A56C0304FB9C37@PEKW933A.cn001.si emens.net>
- References: <44AAB314.email@example.com> <DFBD1C5904D9E647868651D5C6A56C0304FB9C37@PEKW933A.cn001.siemens.net>
[redirected to the openldap-software list]
At 08:17 PM 7/4/2006, Chen, Shi Jun SLC CT PEK wrote:
>Howard Chu wrote:
>>This sounds to me like just using back-ldap all by itself. Why do you
>Think this needs to be an overlay?
>Yes, I can configure slapd.conf to use back-ldap as the backend
>But how can I make back-ldap to select the server dynamically according
>to the concrete content of LDAP request?
>For example, the entries are in the same sub-tree, but are devided in
>three remote DSAs (A, B & C). When the local DSA receives the request on
>entry resided in B, how to use back-ldap to route the request to DSA B?
You configure a separate back-ldap instance for each distinct DIT
context being proxied. Or you configure the local with a single
database (hdb/bdb) holding named references for A, B, C pointed to
the appropriate servers, and then use the chaining overlay. Or
a combination approach.