Re: Deletions not propagating in multi-hop syncRepl environment

["Pierangelo Masarati" <ando@sys-net.it>]

> The 2.3 provider is implemented as an overlay, so it can sit on just
> about any backend. (Come to think of it, you could even run it over
> back-ldap and turn any vendor's LDAP server into a syncrepl provider.)

Provided it supports entryCSN and entryCSN-based searches, entryUUID,
structuralObjectClass (or equivalent; in this case, appropriate mapping is
required).  I'm wondering if adding such a layer (e.g. by means of a
dedicated overlay) could be of use.

back-ldap would provide connectivity, slapo-rwm would provide remapping,
and yet another layer (slapo-muck?) could provide data mucking:
- turn objectClass values into structuralObjectClass
- turn timestamps into entryCSN
- turn any unique attribute value into entryUUID

p.

-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497