Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vRO 7.x service failing to start after replacing vRA certificate (52941)

Last Updated: 3/29/2018Categories: TroubleshootingTotal Views: 6578Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vRealize Orchestrator 7.x service fails to start after replacing the vRealize Automation certificate.

This issue will only affect vRealize Orchestrator instances that leverage vRealize Automation as an authentication provider.

The control center validation shows a number of flags regarding a pending service restart to apply a configuration change.

In the vRO server.log located at /var/log/vmware/vco/app-server, you see the entries similar to:

2018-02-21 15:14:48.536+0100 [Thread-4] WARN  {} [RetriableOperation] Exception handled during retry operation with message: I/O error on GET request for "https://vRA_FQDN/component-registry/endpoints/types/sso": java.security.cert.CertificateException: Untrusted certificate chain.; nested exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Untrusted certificate chain

Note:The above log extract is only an example date and timestamp may vary, the key point here is that the SSO component registry url is referenced and that the message complains about an untrusted certificate.

Cause

This issue occurs because the vRealize Orchestrator certificate store has the old vRealize Automation certificate stored for the Authentication alias vco.cafe.component-registry.ssl.certificate.

Resolution

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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant