Este contenido no está disponible en el idioma seleccionado.

Chapter 22. Setting up content synchronization using the SyncRepl protocol


To support the SyncRepl protocol according to RFC 4533, Directory Server uses the Content Synchronization plugin. With the Content Synchronization plugin, LDAP servers and clients can use Red Hat Directory Server as a source to synchronize their local database with the changing content of the directory.

To use the SyncRepl protocol, you need to perform the following configurations:

  • On the Directory Server side:

    • Configure the Content Synchronization and Retro Changelog plugins. The Retro Changelog plugin must log the nsuniqueid operational attribute.
    • Optional: Create a new user that your client will use to bind to Directory Server. The new user must have permissions to read the content in the directory. For details, see Adding an LDAP entry using the command line.
  • Configure your client. For example, set the search base for a subtree to synchronize. For further details, see your client’s documentation.

The following procedure configures the Content Synchronization and Retro Changelog plugins by using the command line.

Prerequisites

  • You have root permissions.

Procedure

  1. Verify if the Retro Changelog is enabled:

    # dsconf <instance_name> plugin retro-changelog show
    ...
    nsslapd-pluginEnabled: off
    Copy to Clipboard Toggle word wrap

    If the Retro Changelog plugin is disabled, enable it:

    # dsconf <instance_name> plugin retro-changelog enable
    Enabled plugin 'Retro Changelog Plugin'
    Copy to Clipboard Toggle word wrap
  2. Add the nsuniqueid operational attribute with the targetUniqueId alias to the Retro Changelog plugin configuration:

    # dsconf <instance_name> plugin retro-changelog add --attribute nsuniqueid:targetUniqueId
    Successfully changed the cn=Retro Changelog Plugin,cn=plugins,cn=config
    Copy to Clipboard Toggle word wrap
  3. Optional: Apply the following recommendations to improve performance:

    1. Configure the maximum age of the Retro Changelog entries. For example, set the age to 2 days (2d):

      # dsconf <instance_name> plugin retro-changelog set --max-age 2d
      Successfully changed the cn=Retro Changelog Plugin,cn=plugins,cn=config
      Copy to Clipboard Toggle word wrap
    2. If you know which backend or subtree your client accesses to synchronize data, limit the scope of the Retro Changelog plugin. For example, to exclude the cn=marketing,dc=example,dc=com subtree, enter:

      # dsconf <instance_name> plugin retro-changelog set --exclude-suffix "cn=marketing,dc=example,dc=com"
      Successfully changed the cn=Retro Changelog Plugin,cn=plugins,cn=config
      Copy to Clipboard Toggle word wrap
  4. Enable the Content Synchronization plugin:

    # dsconf <instance_name> plugin contentsync enable
    Enabled plugin 'Content Synchronization'
    Copy to Clipboard Toggle word wrap
  5. Optional: Adjust the ACI to limit who can use the SyncRepl control. By default, Directory Server creates the following access control instruction (ACI) in the oid=1.3.6.1.4.1.4203.1.9.1.1,cn=features,cn=config entry that enables all users to use the SyncRepl protocol:

    aci: (targetattr != "aci")(version 3.0; acl "Sync Request Control";
       allow( read, search ) userdn = "ldap:///all";)
    Copy to Clipboard Toggle word wrap

    For details about how to adjust the ACI, see Defining ACI bind rules.

  6. Restart the server:

    # dsctl <instance_name> restart
    Copy to Clipboard Toggle word wrap

Now your clients can synchronize data with Directory Server by using the SyncRepl protocol.

Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat