Controlling access to the agent
This section details how to manage access to the agent. Through an access control list (ACL), the agent allows you to define the following:
- Who has access to the agent
- What hosts have access to the agent
- What type of PATROL consoles and utilities have access to the agent, and any combination of these three types of control
The actual log ons are subject to account and password validation. Even with the most lenient access control list (all users from all hosts in any type of mode), you cannot log on with an unknown account.
Backing up your configuration files before defining an ACL
Before creating an ACL, back up your agent configuration file (config.default), which contains installation default values, and your agent configuration change file (user-defined_filename.cfg), which contains any customizations that you made to agent configuration variables. Copy and save these files outside the PATROL directory structure.
Backing up these files ensures that you can restore the agent to its previous state if your ACL definitions produce unexpected or undesirable results.
Performing actions related to ACL
- Defining Access Control Lists
- Denying access to the agent
- Controlling the system output window display
- HostName and UserName attribute conventions
- Connection modes and accounts
- Required access
- Restoring access in case of lockout
- Access for agent configuration utility started through Developer Console
- Access for Agent configuration utility started from the command line
- Controlling pconfig access to the agent
- Securing PATROL Agent from the pconfig clients
- Access for PATROL Event Manager console
- Access for the KM scripts
- Access for PEM applications
- Error messages
- Controlling events displayed in PEM
- Using the user account for PEM commands
- Controlling the configuration of PATROL Agent
Log in or register to comment.