There are times you need to point your A2A client to a different PAM server and you end up having an error. This article indicates a possible cause for this behaviour and suggests a possible solution.
If you have previously used your Client installation for one server and are now pointing it to a different server, you must delete the following cache file before starting the Client daemon again:
where $CSPM_CLIENT_HOME is your installation directory, for example /opt/cloakware
Here you can find the instructions how to proceed
CA PAM all versions
To reconfigure a Password Authority Client (A2A) to use a different PAM Server:
1. Stop the Password Authority Client (read below how to start and stop the Client).
2. Go to $CSPM_CLIENT_HOME/cspmclient/config/data.
3. Delete .cspmclient.dat.
4. Update the <cspmserver> entry in the Client configuration with your new server name. For example:
The config.xml file is located in $CSPM_CLIENT_HOME/cspmclient/config/cspm_client_config.xml where $CSPM_CLIENT_HOME is your installation directory, for example /opt/cloakware.
To stop the Password Authority Client: