Re: Replication from OpenLDAP to Fedora 389 DS

To: Dieter Klünter <dieter@dkluenter.de>

Subject: Re: Replication from OpenLDAP to Fedora 389 DS

From: Italo Valcy <italovalcy@gmail.com>

Date: Tue, 25 Feb 2014 18:24:14 -0300

Cc: openldap-technical <openldap-technical@openldap.org>

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Wy8qwNTkLCF6ttMbUeDvEOU43o2BfVEUkQP0Jl2Q1ig=; b=T0k0Tn1r0/mjs4Ew+gpPD9kPrjCU+7o6aSnwI8rjlwrS7dkRh6D6c/+PhkTxMgQkLC kjPdHJCTxKofO66iSyW19msGWqsq2REmkyyE2ft/Wf8YcTkwQ/S/XfGMpBOYV08mea3i yzgtyxpD3VoP8KGhbTUL1ZM3jHtBqpnOVDD7khiHaFUdbEES3JAJZ2bY1wusLklz93xP Nb6AlsO4z7a0wUIxmNBk9m+bSCw5YVHwO4+AP9vR3+WTSWGSY8Ks2XaiFo9TPwM+ePgm gO5lEM6fwZS5cVwFPrmwuyGpe6ckCyO+MeeXSnWso1XkpCROHN1O9BFsyF2CuISG04fc HAOA==

In-reply-to: <20140225210547.3e6ba31f@pink.avci.de>

References: <CAJBgHoZb9LcAMLp9hETvxvunHC-594_SLdpd6WXtMKoH85b7Dg@mail.gmail.com> <20140225110435.644598c0@pink.avci.de> <CAJBgHoaBqJeYmNX07Wj_cB5yJpnKRTe2142DRXQWHM8HEt+Yzw@mail.gmail.com> <20140225145028.1dfc4952@pink.avci.de> <CAJBgHoYq_P5t5js=MRsJ1LDM7YFx2y7uFGC-AW-HWP3mo5jr0w@mail.gmail.com> <20140225210547.3e6ba31f@pink.avci.de>

Hello Dieter,

On Tue, Feb 25, 2014 at 5:05 PM, Dieter Klünter <dieter@dkluenter.de> wrote:

No, syncrepl (consumer) does not reqire operational attributs. Only if
the ldap backend is also defined as syncprov (provider), than some
operational attributes are required in order to provide valid data.
But I don't think that the fedora directory supports RFC 4533.

Thanks for the reply!

Yes, but this is the only way the documentation points to in order to have a push-based replication initiated by the provider, do you agree? Bellow is part of OL documentation:

18.2.4. Syncrepl Proxy Mode

While the LDAP Sync protocol supports both pull- and push-based replication, the push mode (refreshAndPersist) must still be initiated

from the consumer before the provider can begin pushing changes (...) This mode can be configured with the aid of the LDAP Backend

(Backends and slapd-ldap(8)). Instead of running the syncrepl engine on the actual consumer, a slapd-ldap proxy is set up near (or

  collocated with) the provider that points to the consumer, and the syncrepl engine runs on the proxy.

  18.2.4.1. Replacing Slurpd

  The old slurpd mechanism only operated in provider-initiated push mode. Slurpd replication was deprecated in favor of Syncrepl replication

and has been completely removed from OpenLDAP 2.4.

Using the old slurpd, it was possible to filter which attributes I would like to send to the consumer. But, as far as could understand, this

workaround is not possible with the above proposal (from doc).

Do you see any other way to achieve this feature?

Kind regards, Italo.

--
Saudações,

Italo Valcy :: http://wiki.dcc.ufba.br/Main/ItaloValcy