check this out:
How to change the SSL certificate of a vCO Appliance
Best Regards / Поздрави
Spas Kaloferov | Technical Solutions Architect
Thank you, but I have already been through that process (or similar) via other sources on the web. My issue is that the certificate behaves correctly through a web browser (as per the test in your blog page), but not on the vRO Client.
Can you post a screenshot of the [Certification path] tab of the certificate?
You've set you've followed the article above. Did you PFX package contain also the sunnydale-DC01-CA certificate?
I have now been back, started from scratch using your guide rather than the others I used previously, specifically scenario 1 and get the same result. I can happily navigate with a web browser to the vCO server and the certificate looks fine, however the vCO client still prompts about the certificate.
To answer your question about pfx, I am not using a pfx since that is not mentioned in scenario 1 of your guide.
To me it still looks like the issue is with the vCO client as I mentioned earlier referencing this KB:
However, I am unable to carry out the solution since the path to the Orchestrator keystore on the client machine does not appear to exist.
i actually sent you the link for the vCO Appliance. Here for the Windows vCO.
How to change the SSL certificate of Windows installed vCO
Anyway the warning you get in the vCO Client after you change the certificate is expected. Just select to install it and ignore the message. Next time you login you will not receive it, because the vCO Client will be trusting the certificate this time.