This is enhancement made as part of PA 23.3 release documented here
If accessing the PA configuration remotely using pconfig from PA version 23.3 onwards, the credentials are required by default.
For example, pconfig +get -host <patrol agent host name> -p <portnum> -U <username> -W <password>.
This behavior can be changed by setting up the configuration variable /AgentSetup/pconfigRequiresRemoteAuthentication = { REPLACE="false"}.
If /AgentSetup/pconfigRequiresRemoteAuthentication configuration variable is set to True then, remote pconfig command will not work without valid monitoring user credentials.
Detailed explanation below:
- No credentials are required by default when accessing the PA configuration locally using pconfig.
For example, pconfig +get -p <portnum>.
This behavior can be changed by setting up the configuration variable /AgentSetup/pconfigRequiresAuthentication = { REPLACE="true"} or setting up requiresconfigauthentication = true in the patrol.conf file.
For example, pconfig +get -p <portnum> -U <username> -W <password>.
- If accessing the PA configuration remotely using pconfig from PATROL Agent version 23.3 onwards, the credentials are required by default.
For example, pconfig +get -host <patrol agent host name> -p <portnum> -U <username> -W <password>.
This behavior can be changed by setting up the configuration variable /AgentSetup/pconfigRequiresRemoteAuthentication = { REPLACE="false"}.
- PA access on PatrolCli is allowed by using the default account credentials only.