After performing the CDCR configuration, Websecadmin application will have an issue starting due to an incorrect password configuration.
This problem can be fixed with in two cases:
-
Pre-CDCR configuration
-
Post CDCR configuration
1) Pre-CDCR configuration
To fix the above issue before starting the CDCR configuration, run the following command on all webapp nodes as either veridiumid user or root user:
sed -i "717s|HAPROXY_PUBLIC_CERT_P12_BASE64|WEBSERVICE_KEYSTORE_P12_BASE64|g" /etc/veridiumid/script/veridiumid_cdcr.sh
2) Post CDCR configuration
If the issue is noticed after finishing the CDCR configuration then run the following commands on all webapp nodes as root user in order to apply the fix:
# Download Zookeeper configuration
bash /opt/veridiumid/migration/bin/migration.sh -d /tmp/zoo_bkp
# Change certificate for Websecadmin
/opt/veridiumid/setupagent/bin/yq '.variables.WEBSERVICE_KEYSTORE_P12_BASE64' /tmp/zoo_bkp/infra/tenant-infra.yaml | base64 -d > /opt/veridiumid/websecadmin/certs/admin_keystore.p12
# Cleanup temporary files
rm -rf /tmp/zoo_bkp
# Restart Websecadmin
systemctl restart ver_websecadmin