Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual page 129

Creating and Maintaining Database Links
The client application sends a modify request to Server 1. Server 1 contains a
database link that forwards the operation to Server 2, which contains another
database link. The database link on Server 2 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 1, 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 2.
Consider the following example scenario. On Server A, a directory tree is split as
follows:
Chapter 3 Configuring Directory Databases 129