Red Hat DIRECTORY SERVER 8.1 - DEPLOYMENT Deployment Manual page 79

Figure 5.11. Sending a Client Request to a Server Using Referrals
In the illustration above, the client application performs the following steps:
1. The client application first binds with Server A.
2. Server A contains an entry for the client that provides a user name and password, so it returns
a bind acceptance message. In order for the referral to work, the client entry must be present on
server A.
3. The client application sends the operation request to Server A.
4. However, Server A does not contain the requested information. Instead, Server A returns a referral
to the client application instructing it to contact Server B.
5. The client application then sends a bind request to Server B. To bind successfully, Server B must
also contain an entry for the client application.
6. The bind is successful, and the client application can now resubmit its search operation to Server
B.
This approach requires Server B to have a replicated copy of the client's entry from Server A.
Performing Search Requests Using Chaining
The problem of replicating client entries across servers is resolved using chaining. On a chained
system, the search request would occur as follows:
Deciding Between Referrals and Chaining
69