NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
S-12
User IDs
NonStop SQL/MP objects, SQL programs in Guardian files, and other Guardian files
can optionally use the Safeguard security management facility, a product that provides
security features beyond those of standard Guardian security. The Safeguard subsystem
can secure NonStop SQL/MP objects at the volume or subvolume level and can secure
all other Guardian files at the volume, subvolume, or file level.
SQL programs in OSS files and other OSS files use OSS security, which differs from
Guardian security. A user who runs an SQL program in an OSS file has both an OSS
identity (which determines the user's authorization to access OSS files) and a
corresponding Guardian identity (which determines the user's authorization to access
NonStop SQL/MP objects and other Guardian files).
The remainder of this entry describes the general principles of Guardian security as they
relate to access to NonStop SQL/MP objects, including access from both Guardian and
OSS NonStop SQL/MP programs. For more detailed information about Guardian,
Safeguard, and OSS security, see the Guardian User's Guide, the Safeguard Reference
Manual, and the OSS User's Guide.
User IDs
Each user authorized to log on to a node in a Tandem NonStop network is identified by a
Guardian user ID that consists of a Guardian group number and Guardian user number
and that corresponds to a Guardian group name and Guardian user name.
The Guardian user ID is the combination of the group number and user number (not the
user number alone) or the combination of the group name and user name (not the user
name alone). The user ID is normally represented in one of the following forms:
8,55 <-- Group number, comma, user number
DEVEL.JIM <-- Group name, period, user name
A user of a Tandem NonStop system must specify a Guardian user ID and an
accompanying password to log on to a NonStop system through a TACL process. A user
who uses the OSS environment of a NonStop system might also have a different form of
user ID for the OSS environment, but each OSS user ID or alias is associated with a
Guardian user ID of the form just described.
Group Manager and Super ID
Each Guardian group includes one special user ID called the group manager that has
user number 255 and normally (by convention) has the user name MANAGER; for
example:
The group manager can act as the owner of any object or file owned by another member
of the group. Each node has one special user ID called the super ID that has Guardian
8,255 <-- Typical group manager ID number
DEVEL.MANAGER <-- Typical group manager ID name