HP OpenView Operations Administrator's Reference - filibeto.org

About Remote Access
About OVO Security
About Security in OVO Operations
This section describes security for remote login and command execution
in UNIX and MPE/iX environments.
For more information on user accounts, access to files, and general file
permissions, see “About File Access and Permissions” on page 495.
Starting Applications and Broadcast Commands
If OVO operators do not log in with the default user account set up by the
OVO administrator, they must use the corresponding passwords for
broadcasting commands or starting applications. If operators do not use
the correct passwords, the command or application will fail.
Starting I/O Applications
When starting applications configured as Window (Input/Output),
operators must do one of the following:
Specify passwords with the application attributes.
Provide .rhosts entries or /etc/hosts.equiv functionality.
Specify passwords interactively.
About Passwords on DCE Managed Nodes
NOTE DCE managed nodes are not supported on Solaris.
When executed on the management server with the -server option, the
OVO utility opc_sec_register_svr.sh creates a special user name
(principle) opc-agt-adm. This user name has the permissions needed to
modify accounts on the managed node.
Normally, the OVO agents log into DCE at startup using the primary
principal opc/opc-agt/. However, if this login fails for any
reason, the OVO control agent then attempts to login as opc-agt-adm,
and to generate a new random password for its primary account. The
new password updates both the DCE registry and the local keytab file.
Chapter 12 505