7.3

4 You may need to run the following commands to trust the certificate:
/var/lib/vco/tools/configuration-cli/bin/vro-configure.sh trust --uri https://vra.domain.com
/var/lib/vco/tools/configuration-cli/bin/vro-configure.sh trust --registry-certificate --uri
https://vra.domain.com
5 Ensure that the vRealize Automation certificate is now injected into the vRealize Orchestrator trust
store using the following command:
/var/lib/vco/tools/configuration-cli/bin/vro-configure.sh list-trust
6 Start the vRealize Orchestrator server and control center services.
service vco-server start
service vco-configurator start
Update External vRealize Orchestrator to Trust
vRealize Automation Certificates
If you update or change vRealize Automation appliance or IaaS certificates, you must update
vRealize Orchestrator to trust the new or updated certificates.
This procedure applies to vRealize Automation deployments that use an external vRealize Orchestrator
instance.
Note This procedure resets tenant and group authentication back to the default settings. If you have
customized your authentication configuration, note your changes so that you can re-configure
authentication after completing the procedure.
See the vRealize Orchestrator documentation for information about updating and replacing
vRealize Orchestrator certificates.
If you replace or update vRealize Automation certificates without completing this procedure, the
vRealize Orchestrator Control Center may be inaccessible, and errors may appear in the vco-server and
vco-configurator log files.
Problems with updating certificates can also occur if vRealize Orchestrator is configured to authenticate
against a different tenant and group than vRealize Automation. See
https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=2147612.
Procedure
1 Stop the vRealize Orchestrator server and Control Center services.
service vco-configuration stop
Managing vRealize Automation
VMware, Inc. 21