SeeView Server Gateway (SSG) Manual

SSG Commands
HP NonStop SeeView Server Gateway (SSG) Manual—526356-004
4-6
SECURE Command
dynamically update the access rules enforced by an existing SSG process. Unlike the
SET SECURE command, the SECURE command does not alter the SSGCOM
security settings, so access rights specified via the SECURE command are not
communicated to a new SSG at startup. Use the SET SECURE command to define
default CI access rules that communicated to a new SSG when it is created.
node
is the node name on which the target SSG is running. The new SECURE data is
sent to the SSG process given by the current ID on the target node. If an asterisk
(*) is specified for the node name, the new SECURE data is sent to the SSG
process given by the current ID on every node in the network. If no node name is
specified, the current node is used.
CI
is an optional keyword indicating that what follows is a simple command interpreter
name (for example, ASAP, FUP, and so forth). The keyword CI is optional. For
instance, SECURE ASAP ANY is equivalent to SECURE CI ASAP ANY.
object
specifies the simple name of the affected command interpreter; for example, FUP,
SCF, and so forth. If a SECURE command is entered for a previously defined CI,
the prior setting is replaced with the new value.
DEFAULT
specifies the default security setting and does not affect settings for the existing list
of command interpreters. The DEFAULT setting is used to establish access rights if
a specific definition does not exist for a given CI object.
*
can be used to indicate that all previously defined command interpreter objects are
affected. For example, SECURE * USER applies to all CIs that were previously
defined using SECURE commands and sets the security attribute for each to
USER. This command also alters the DEFAULT setting.
ANY
indicates that any user is allowed to access the CI, regardless of their user
identification.
SECURE [\node|\*] {[ CI ] object} ANY | GROUP | USER | SUPER | NONE | CLEAR
{DEFAULT }
{* }