Using PAC for interagent communication
This parameter defines security when agents communicate with each other (that is, if the Access Control PAC) handshake is to be used for interagent communication). Be aware that PAC communication is not possible between a current agent and a 6.0 or earlier agent. By default this parameter is set to No/0, to make sure all agents can communicate with each other when upgrading.
If you would like to use access control for agent communication you must activate this option for the master as well as all agents (that is, during the master step 16 and relay step 10 installations explained in the installation topic as well as for the agent rollout in the rollout topic.
The following options are available for access control:
Parameter | Description |
|---|---|
Receive Both, No PAC Connections | As server, allow PAC connections with client authentication as well as non-PAC connections. As client, no PAC connections are required. |
Receive Both, PAC Connections | As server, allow PAC connections with client authentication as well as non-PAC connections. As client, only allow PAC connections. |
Yes | Only allow PAC connections (as server or client). |
Yes (With server authentication) | Only allow PAC connections (as server or client) with mutual authentication. |
The following topics are provided:
Installing the master agent with access control
To install the master agent with access control proceed as follows:
- At step 16, make the following additional selection:
In the HTTP Port Configuration window, select the desired option from the PAC box. Then proceed with the next step as defined for the rest of the procedure.
Installing the relay agent with access control
To install the relay agent with access control, proceed as follows:
- At step 10, make the following additional selection:
In the Agent Configuration dialog, select Yes from the PAC box. Then proceed with the next step as defined for the rest of the procedure.
Comments
Log in or register to comment.