HP OpenView Operations Administrator's Reference - filibeto.org

About OVO Process Security
About OVO Security
About Network Security
In OVO, the management server and the managed nodes simultaneously
run both RPC clients and servers. As a result, OVO reduces the process
configuration information needed to execute RPC calls.
To execute an RPC call, OVO needs the following configuration
information about a process:
❏ Name and password
❏ Security level
This configuration information must be present on both the management
server and the managed node.
Types of OVO Process Names
In the context of DCE, OVO associates just two names (or principals)
with the two types of node in its environment:
❏ Management Server
Processes run under the name associated with the management
server.
❏ Managed Node
Processes relating to the managed node in question run under the
identity of the name associated with the managed node.
For example, if the OVO management server garlic.spices.com and
the managed node basil.herbs.com are configured to run with
authenticated RPCs, the following principals are created:
❏ opc/opc-mgr/garlic.spices.com
❏ opc/opc-agt/basil.herbs.com
About OVO Process Groups
In DCE, a name or principal (garlic.spices.com) belongs to a group
(opc-mgr), which in turn belongs to an organization (opc). The only
exception to this rule in OVO is the principal opc-agt-adm, which is a
member of the group and organization none, special principal that is
primarily used in the administration of accounts and passwords.
Chapter 12 491