8 Responses

  1. Behruz
    Behruz at |

    Hey Michael,

    thank you for great posts about certificates and their installation in vmware environment.

    i have changed inventory and web client certificates and reregistered vcenter in admin-app but still have same certificate error as on your screenshot. Meanwhile certificate in the address bar is accepted by browser itself. re-registering doesn't help

    any ideas?

    thanks

    Reply
    1. @vcdxnz001
      @vcdxnz001 at |

      Hi Behruz, I've had this before as well. The customer rebooted their system in one instance and the problem went away. Did you check that when vCenter was registered again the correct thumbprint was loaded? You should find after restarting the services, or rebooting the vSphere Web Client, that the error goes away. You may have to re-register again and double check the thumbprint is the correct one for the vCenter certificate.

      Reply
  2. Behruz
    Behruz at |

    I have tried to restart system re-register vcenter 10 times and it doesn't help when I posted my frist question to you regarding Web Client I have used esxi instruction to generate certificates for vCenter and Web Client, afterwards I have realized that I have missed another instruction from you for vCenter. Today I have prepared new certificates for vCenter, Update Manager (I'm using same certificate files for Web Client from vCenter) and I'm still have problem with Web Client. I have compared thumbprint and they are the same in warning windows from Web Client and certificate itself. My another problem is the VMware vSphere Profile-Driven Storage Service fails to start.

    Reply
  3. Updating CA SSL Certificates in vSphere 5 « Long White Virtual Clouds

    […] vSphere Web Client SSL Cert not updated after vCenter SSL Cert Changed […]

  4. Erik Bussink
    Erik Bussink at |

    Hiya Michael,

    Thanks for this great tip to also place the SSL certs in the Web Client directory.

    Thanks.

    Reply
  5. Why change VMware default self-signed SSL certs? « Long White Virtual Clouds

    […] to change the self-signed SSL certs in a few of the VMware components, such as vCenter Server 5, vSphere Web Client, and ESXi 5 Hosts. All without any discussion about why you would want to do it at all. So why do […]

  6. Dan Corrigan
    Dan Corrigan at |

    If you have a password protected private key, you will have to edit the password used for your pfx in D:Program FilesVMwareInfrastructurevSphere Web ClientDMServerconfigtomcat-server.xml

    You also have to update D:Program FilesVMwareInfrastructuretomcatconfserver.xml

    Reference:
    http://kb.vmware.com/kb/1013472

    BTW, Great articles!

    Reply
    1. @vcdxnz001
      @vcdxnz001 at |

      Thanks Dan. I have updated the article with reference through to the VMware KB. I have not used this in the past as I don't believe it offers any additional security as the password is still contained in clear text in the configuration files. But I do acknowledge some companies security policy makes this mandatory. In a vSphere environment there are multiple tomcat instances and configuration files that would need to be updated. Not all of them are obvious, not all of the passwords are documented, and changing them is not always supported. Great care needs to be taken if you are changing from default settings. Thanks very much for the comment it is greatly appreciated.

      Reply

Leave a Reply