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

Re: chaining for a single backend?

Quanah Gibson-Mount wrote:

--On Tuesday, February 09, 2016 9:53 AM +0100 Marc Patermann
<hans.moser@ofd-z.niedersachsen.de> wrote:


Am 08.02.2016 um 22:33 Uhr schrieb Quanah Gibson-Mount:

--On Monday, February 08, 2016 4:50 PM +0100 Marc Patermann
<hans.moser@ofd-z.niedersachsen.de> wrote:

Am 30.12.2015 um 11:49 Uhr schrieb Marc Patermann:

I want to activate chaining for a single backend.

The server is a replication consumer and has a few glued database
backends. Only one is containing linux accounts with ppolicy overlay.
This should use chaining to replicate the ppolicy changes which
otherwise stay local.

Can this be achieved?

I would like to come back to this.

Here is our example with multiple glued databases and chaining.
First there is the "full chain" where chain is loaded globally and
should work for all database backends. This works.

Then there is the example where chain is loaded in the linux database
backend. This does not chain the request to the master.


OpenLDAP version?

last tested with 2.4.43



Ok.  On the surface it looks right to me, but I've never used slapo-chain. I
hope someone who has more knowledge on it can chime in. :/
Chaining intercepts referrals and chases them down. The overlay has to be positioned at the same place (or above) wherever the referrals are generated, in order to intercept them. Referrals generated by the updateref directive are produced in the frontend, therefore the only way for the slapo-chain overlay to have a chance to see them is by being configured on the frontend.
Configuring slapo-chain on a specific backend will only affect referral entries stored in that backend. 

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/