On a cluster, all elements of the user authorization
data should exist in a common database. These authorization elements
include the system user authorization files (SYSUAF.DAT and its backup
SYSUAFALT.DAT), the rights database (RIGHTSLIST.DAT), the network
authorization file (NETPROXY.DAT) and its object database file (NETOBJECTS.DAT),
which are present on all OpenVMS systems, and optionally, the autologin
A secure cluster requires that the authorization
data be synchronized across all nodes. If a site chooses to maintain
multiple versions of these files, then you must synchronize the data.
Each user should have the same UIC, group number, and set of identifiers
defined on every node. Coordination of privileges and access rights
is also critical. A shared disk is protected only as much as its least
protected node. If you maintain separate authorization files on each
node in the cluster, ensure that user privileges are common across
all copies of the system user authorization file (SYSUAF.DAT). “Fields in SYSUAF.DAT Requiring Synchronization” lists the fields
of SYSUAF.DAT that must be identical on each node.
Table 12-4 Fields in SYSUAF.DAT Requiring Synchronization
| Internal Name|| $SETUAI Item Code|
Use SYSMAN if you choose to create an autologin
file and maintain the file in the common authorization database with
your authorization files and rights database. On clustered systems,
the autologin file must include the cluster node name as a prefix
to the terminal name. For example, the terminal TTA0 on node WILLOW
would be represented as WILLOW$TTA0. See “Using the System Management Utility” for an overview of SYSMAN.