HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

• “Summary of cascading chaining configuration attributes” (page 82)
• “Cascading chaining configuration example” (page 82)
2.4.8.1 Overview of cascading chaining
Cascading chaining occurs when more than one hop is required for the directory to process a
client application's request.
The client application sends a modify request to Server 1. Server one 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, 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.
For example, on Server A, a directory tree is split:
2.4 Creating and Maintaining Database Links 77