Red Hat Directory Server 8.0 Administrator's Guide

The client application sends a modify request to server one. Server one contains a database
link that forwards the operation to server two, which contains another database link. The
database link on server two forwards the operations to server three, which contains the data the
clients wants to modify in a database. Two hops are required to access the piece of data the
client want to modify.
During a normal operation request, a client binds to the server, and then any ACIs applying to
that client are evaluated. With cascading chaining, the client bind request is evaluated on server
one, but the ACIs applying to the client are evaluated only after the request has been chained to
the destination server, in the above example server two.
Consider the following example scenario. On server A, a directory tree is split as follows:
Chapter 3. Configuring Directory Databases
94