Whenever the Directory Proxy Server forwards a request to the backend set containing the user's entry, it forwards the request with an authorization identity that reflects the user's actual identity, since servers in that set already know about that user. However, when forwarding a request to a backend set that does not contain the user's entry, the Directory Proxy Server uses an alternate authorization identity that reflects the generic user with the same set of rights as the actual user issuing the request. Alternate authorization identities allow for the proper evaluation of access control rules for users whose entries are not present within an entry-balanced dataset.
- uid=normal user,dc=example,dc=com
Returning to the example scenario, the client with
uid=5000 binds to the
Directory Proxy Server, which sends a BIND request to entry-balancing
set-01. Next, the client sends a SEARCH request for
uid=15000. The Directory Proxy Server determines that
uid=15000 lives on
entry-balancing set-02. Next, the Directory Proxy Server then determines that
uid=5000 does not have an entry on entry-balancing set-02. The
Directory Proxy Server uses an alternate authorization identity that
reflects the generic user,
uid=normal user, which has the same set of rights as
uid=5000 who is issuing the request. The access control is accepted
and the SEARCH request returns a response for
Whenever a user authenticates to the Directory Proxy Server, the server can keep track of which backend set holds that user's entry and determine whether an alternate authorization identity is required. The server can also determine which of these generic accounts best describes the rights that the user should have.