Red Hat Directory Server 8.0 Administrator's Guide

another server), this entry must be specified as the one authorized to perform replication
updates.
• The replication agreement is created on the supplier server, the DN of this entry must be
specified in the replication agreement.
• The supplier bind DN entry must not be part of the replicated database for security reasons.
• This entry, with its special user profile, bypasses all access control rules defined on the
consumer server for the database involved in that replication agreement.
NOTE
In the Directory Server Console, this replication manager entry is referred to as
the supplier bind DN, which may be misleading because the entry does not
actually exist on the supplier server. It is called the supplier bind DN because it is
the entry which the supplier uses to bind to the consumer. This entry actually
exists, then, on the consumer.
For more information on creating the replication manager entry, see Section 3, “Creating the
Supplier Bind DN Entry”.
1.6. Replication Agreement
Directory Servers use replication agreements to define their replication configuration. A
replication agreement describes replication between one supplier and one consumer only. The
agreement is configured on the supplier server and must specify all required replication
information:
• The database to be replicated.
• The consumer server to which the data is pushed.
• The days and times during which replication can occur.
• The DN and credentials that the supplier server must use to bind (the replication manager
entry or supplier bind DN).
• How the connection is secured (SSL, client authentication).
• Any attributes that will not be replicated (fractional replication).
1.7. Compatibility with Earlier Versions of Directory Server
The replication mechanism in Directory Server 8.0 is different from the mechanism used in 4.x
Replication Agreement
269