Red Hat Directory Server 8.0 Administrator's Guide

The command to restart the Directory Server on platforms other than Red Hat Enterprise Linux is described in

Section 3, “Starting and Stopping Servers”.

plug-in:

aci: (targetattr "*")(target="ldap:///ou=customers,l=us,dc=example,dc=com")

(version 3.0; acl "RefInt Access for chaining"; allow

(read,write,search,compare) userdn = "ldap:///cn=referential integrity

postoperation,cn=plugins,cn=config";)

3.1.1.2. Chaining Component Operations from the Command-Line

1. Specify components to include in chaining using the nsActiveChainingComponents attribute

in the cn=config,cn=chaining database,cn=plugins,cn=config entry of the

configuration file.

For example, to allow the referential integrity component to chain operations, add the

following to the database link configuration file:

nsActiveChainingComponents: cn=referential integrity

postoperation,cn=components,cn=config

See Table 3.2, “Components Allowed to Chain” for a list of the components which can be

chained.

2. Restart the server for the change to take effect.

service dirsrv restart instance

3. Create an ACI in the suffix on the remote server to which the operation will be chained. For

example, this creates an ACI for the Referential Integrity plug-in:

aci: (targetattr "*")(target="ldap:///ou=customers,l=us,dc=example,dc=com")

(version 3.0; acl "RefInt Access for chaining"; allow

(read,write,search,compare) userdn = "ldap:///cn=referential

integrity postoperation,cn=plugins,cn=config";)

3.1.2. Chaining LDAP Controls

It is possible to not chain operation requests made by LDAP controls. By default, requests made

by the following controls are forwarded to the remote server by the database link:

• Virtual List View (VLV). This control provides lists of parts of entries rather than returning all

entry information.

• Server-side sorting. This control sorts entries according to their attribute values.

Configuring the Chaining Policy