Configuration Guide User Manual

Micro-PWC CONFIGURATION GUIDE
@aGlance/IT Server Interface 317
11.4 Security for the @aGlance/IT Server
The two aspects to security for the @aGlance/IT API for the Micro-PWC are:
• Client access to the @aGlance/IT server for Micro-PWC
• Access to the Micro-PWC server database
11.4.1 Security for Access to the @aGlance/IT Server for Micro-PWC
Client proxy definition is used to specify which clients are permitted to access the server applications on
the local node. A client proxy account is a mapping from a remote host name and user ID to a local ID. Cli-
ent proxies are configured on the node in which the @aGlance/IT server for Micro-PWC is installed. Client
proxy definition is performed using the @aGlance/IT aag_admin utility. (Access to the aag_admin utility is
described in Section 11.2.3, Registering Client Nodes in this section.) There are three types of client proxy
accounts:
• Separate proxy account for a user on a remote node
• Single proxy account for all users on a remote node
• Single proxy account for all users on all remote nodes
The simplest procedure is to set up a single account for all users on all remote nodes. The default proxy is
called AAG. To use this default proxy, configure a Micro-PWC user named AAG, using user login configura-
tion. The desired Access Level and area permissions should be configured for the user named AAG.
Client proxy definition is a function of the aag_admin utility provided by Axeda Systems Incorporated; it
does not contain provisions for passwords on client proxy accounts. Security is based on the @aGlance/IT
server for Micro-PWC matching the remote node and user names with the local proxy configuration at run
time.
See subsection Section 11.2.3, Registering Client Nodes for details on how to access the aag_admin util-
ity. See the @aGlance/IT online help subsystem for information on client proxies and how to configure
them.
11.4.2 Security for Micro-PWC Database Access
Database access security for the @aGlance/IT server for the Micro-PWCs is based on the Access Level
and area permissions configured on the remote node for the user running the @aGlance/IT client software.
The Access Level and area permissions correspond to the local user name specified in the @aGlance/IT
proxy account. Each session can be associated with a different proxy account.