Hello, is it possible with OpenLDAP to use a filter
objectclass=abc
as filter for syncrepl when abc is an auxiliary object class?
This would mean: - When an entry is created on the master with e.g. object class "country" the entry is NOT replicated. - Later, when you modify this entry by adding the auxiliary object class "abc", the entry will be replicated (added) to the consumer. - Later, when you modify this entry by deleting the auxiliary object class "abc", the entry will deleted from the consumer.
Means: A MODIFY operation in LDAP (client ---> server) can result in an ADD or DELETE operation in the replication protocol (server ---> server).
I ask this because I know at least one X.500 based product (using X.500 DISP for replication) which can't handle this situation ...
Regards, Jochen.
Keutel, Jochen wrote:
is it possible with OpenLDAP to use a filter
objectclass=abc
as filter for syncrepl when abc is an auxiliary object class?
Yes, why don't you simply try? ;-) I did with RE23 and it works. You may run into some issues when having nested objects in a tree hierarchy though. Depends on your data.
Means: A MODIFY operation in LDAP (client ---> server) can result in an ADD or DELETE operation in the replication protocol (server ---> server).
syncrepl is a protocol initiated by the client. AFAIK in standard mode it just detects that an entry as a whole was changed by searching and then changes are applied locally as needed by the replica itself. delta-syncrepl (less chatty) might have issues with this scenario.
Ciao, Michael.
openldap-software@openldap.org
-
Keutel, Jochen -
Michael Ströder