SeeView Server Gateway (SSG) Manual

SSG Commands
HP NonStop SeeView Server Gateway (SSG) Manual—526356-004
4-7
Considerations
GROUP
causes the SSG to perform group-level authentication. In this case, only users
whose user group matches the user group of the SSG are allowed to access the
CI. For example, if an SSG is running under the user ID OPS.ADMIN, only users
who are members of the OPS group are permitted to access a CI defined with
GROUP security.
USER
causes the SSG to perform user-level authentication. In this case, only users
whose ID exactly matches the ID of the SSG are allowed to access the CI. For
example, if an SSG is running under the user ID OPS.ADMIN, only the
OPS.ADMIN user is permitted to access a CI defined with USER security.
SUPER
indicates that only members of the SUPER group are allowed to access the CI,
regardless of the ID under which the SSG is running.
NONE
indicates that no users are allowed to access the CI.
CLEAR
either clears a command interpreter from the list of command interpreters, or else
clears the DEFAULT setting to factory settings if DEFAULT was specified
Considerations
•
The SECURE command does not alter the list of access rights maintained by
SSGCOM itself (that is, the values configured using the SET SECURE command).
Any settings defined via the SECURE command are not communicated to any
SSG processes subsequently started by SSGCOM. To define the rules
communicated to new SSG processes, use the SET SECURE command. The
SECURE command is intended solely to update the access rules enforced by an
existing SSG process.
•
The SSG process to which the SECURE data is sent is defined by the current ID.
To send data to a different SSG process, you must first update the ID using the
SET ID command. For example, if the target SSG process is to be $ZOOX, you
must first set the ID to $ZOO by entering SET ID $ZOO. Any subsequent SECURE
data is sent to the SSG process $ZOOX until the ID is changed again.
•
To display the currently defined SECURE settings from the SSG, enter STATUS
SECURE.
•
If SECURERESTRICT is ON, only super-group users can alter CI access rights.