HP OpenView Operations Administrator's Reference - filibeto.org

About OVO Security
About Security in OVO Operations
496
Saving Administrator Output
Any files that are created when the administrator saves report and
application output are owned by the administrator’s UNIX user and
saved in the $OPC_HOME directory if no absolute path is specified.
About GUI Permissions
This section describes permissions in the Motif-based administrator
GUI, the Motif-based operator GUI, and the Java-based operator GUI.
Accessing the Administrator GUI
In the Motif administrator GUI (that is, the GUI that is started when the
OVO user opc_adm logs on), the UNIX process that is used for making
configuration changes, opcuiadm, runs with root permissions. However,
opcuiopadm, the UNIX process that is used for the administrator’s
browser, runs under the UNIX user ID of the user who started the Motif
administrator GUI rather than UNIX user opc_op.
It is neither necessary nor specifically recommended to start the Motif
administrator GUI as a UNIX user with root privileges (user ID 0). In
addition, when saving the output of database reports on the OVO
configuration, the owner of the files that are written is the UNIX user
who started OVO. Otherwise, the behavior of the administrator GUI is
the same as the operator GUI.
Accessing the Motif-based Operator GUI
During installation, the ownership and permissions of the opcrlogin
utility is set as follows:
-r-xr-x--- root opcgrp /opt/OV/bin/OpC/opcrlogin
When opening an OVO Virtual Terminal or starting an OVO
input/output application on a node, OVO uses the.rhosts entry for the
operator’s UNIX user (if present) instead of the entry for user opc_op. By
using the.rhosts entry, OVO enables the operator to log on without
entering a password.
Users start integrated applications (that is, menu items introduced using
an OV Service application or registered actions represented by an OV
Application) from OVO under the operator’s UNIX user, which is not
usually opc_op.
Chapter 12