Safeguard Reference Manual (G06.24+, H06.03+ )

Introduction
Safeguard Reference Manual—520618-013
1-9
Interaction of Local and Remote Users and
Requests
Authentication
The verification of a user’s claimed identity as a valid local user. Authentication might
or might not be followed by logging the user on to the system. That is, authentication is
always a part of logon, but logon does not always occur after authentication.
A user must be authenticated before logon is permitted. Typically, after a user has
been authenticated, a session is started by logging the user on to the system and
initializing a process to function on the user’s behalf.
When a user logs on through a command interpreter, the command interpreter
assumes the identity of the user by adopting the user’s user ID as its PAID (process
accessor ID).
Local User
A term used in this manual to refer to a locally authenticated user. A process belonging
to a user who has been authenticated by the local system.
Remote User
A term used in this manual to refer to either a remotely authenticated user or an
unauthenticated user.
Remotely Authenticated User
A valid network user who has been authenticated by a node other than the local node.
Unauthenticated User
A process that lacks a valid user ID; for example, a user who has failed remote
validation in an attempt to access objects on the local node.
Local Request
A local request originates on the same node in which the process receiving the request
is running.
Remote Request
A remote request made in relation to the process receiving the request. This request
originates on another node in a network.
Interaction of Local and Remote Users and Requests
In determining whether to audit a request, the Safeguard software considers a local
user making a local request to be a local request. Any request from a remote user is
considered a remote request.