This issue is resolved in VMware vRealize Automation 7.3.0, available at
VMware Downloads.
Workaround:
To work around this issue, verify the certificate and replace with new certificate if required.
Note: Take a snapshot of the vRealize Orchestrator appliance before manually making changes to the trust store.
- Verify the trusted certificates from the vRO trust store.
- To list the trusted certificates, navigate to below locations:
cd /var/lib/vco/tools/configuration-cli/bin
- Run the below command:
./vro-configure.sh list-trust
- Check for the certificate with the following alias vco.cafe.component-registry.ssl.certificate
Note: This is the certificate of the vRealize Automation that the vRealize Orchestrator has configured as its authentication provider.
- This certificate should match the newly configured vRealize Automation certificate.
- If it is different, change the certificate by running this command:
./vro-configure.sh trust --registry-certificate <path-to-the-certificate-file-in-PEM-format> - Restart the vco-server service.
service vco-server restart