This issue is characterized by the following Symptoms. These symptoms may not arise until after rebooting the appliance.
Note: Similar symptoms will arise whenever the password authority sub-system is not started or not working correctly. Usually restarting the appliance will bring this back into working order, but in this case a simple reboot will not suffice.
The following error message will likely be found in the Tomcat logs:
May 24, 2017 6:42:22 PM com.cloakware.cspm.server.app.ApplicationImpl shutdown SEVERE: Shutting down - DataSourceManager.parseAppClusterConfig No local application addresses found.
The following errors & messages may be found in the Session logs:
Trying to view / connect:
When the Password Authority sub-system first loads it checks the clustering configurations. One of the checks it performs is to make sure that the appliance address is listed in the clustering configuration. When there is no clustering configuration defined this is not a problem. However, when the cluster configuration does not contain the IP address of the appliance the PA sub-system will not load because it assumes the configuration is wrong.
Note: When changing the cluster config this situation is usually validated and won't be saved if it does not exist. This situation would usually arise after making networking config changes. The network changes DO NOT validate the clustering config.
Release: PAMDKT99500-2.7-Privileged Access Manager-NSX API PROXY
In order to resolve this problem the server's address will need to be added to the clustering configuration.
Once the appliance comes back from the reboot the Password Authority sub-system should be working as expected.