Mapping logins for site handler RPC handling

When you use site handler, login mapping is managed from the perspective of the remote server. When you set up login mappings, you specify how logins from the calling, or remote, server map to logins on the local server.

The options are as follows:

Logins from the remote server keep their own names on the local server. For this scheme to work, you must set up a login on the local server for each login that will be issuing RPCs from the remote server.
All logins from the remote server are mapped to a single login on the local server, taking on the identity and privileges of that single login.

Mapping more than one remote login to a single local login is not recommended. It reduces individual accountability on the local server. Audited actions can be traced only to the local login, not to the individual logins on the remote server.
Each login from the remote server is mapped to a specific login on the local server. You can use this option in combination with either of the others. The explicit mappings set up for logins under this option override the mappings established under the other methods.