Red Hat Bugzilla – Bug 1044159
[RFE] Support 'Content Synchronization Operation' (SyncRepl) - RFC 4533
Last modified: 2015-08-03 15:06:13 EDT
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/47388 FreeIPA (bind-dyndb-ldap component) does synchronization between LDAP and external DNS database. Persistent search has some drawbacks for this use case: === Persistent search deficiencies === 1. Persistent search doesn't offer 'signal'/'indication' that all existing records were sent to client already and now the client waits for updates. (I.e. an equivalent of 'Sync Info Message' from [[http://tools.ietf.org/html/rfc4533#section-3.4|RFC 4533 section 3.4.1]].)[[BR]] It seems that there is a workaround for this problem, but it complicates a client application: https://lists.fedoraproject.org/pipermail/389-users/2013-June/015990.html 2. The client application has to dump content of whole LDAP sub-tree to maintain consistency between LDAP and own state (e.g. application-specific database). This dump have to be re-done after any connection failure (and reconnection). === RFC 4533 use cases === 1. More effective bind-dyndb-ldap. 2. (Potentially) A migration path to/from OpenLDAP?
$ rpm -qa | grep 389 389-ds-base-1.3.3.1-9.el7.x86_64 389-ds-base-libs-1.3.3.1-9.el7.x86_64 I verified functionality manually while drafting a test plan. Test coverage is pending.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0416.html