{"id":331,"date":"2012-10-06T04:58:00","date_gmt":"2012-10-06T04:58:00","guid":{"rendered":"http:\/\/atumvirtwordpress.azurewebsites.net\/?p=331"},"modified":"2012-10-06T04:58:00","modified_gmt":"2012-10-06T04:58:00","slug":"upgrading-to-vcenter-5-1-certificate-length","status":"publish","type":"post","link":"https:\/\/avtempwp.azurewebsites.net\/2012\/10\/upgrading-to-vcenter-5-1-certificate-length\/","title":{"rendered":"Upgrading to vCenter 5.1 &#8211; Certificate Length"},"content":{"rendered":"<p>VMware has published information about upgrading to 5.1 and the required length of <a href=\"http:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?language=en_US&#038;cmd=displayKC&#038;externalId=2035623\">host certificates<\/a>. \u00a0In my case, I verified before hand that my certificates were the appropriate length so I proceeded, but as it turns out, my vCenter certificates were not the proper length.<\/p>\n<p>Our vCenter was installed first with version 4, which auto-generated self-signed certificates which we never bothered to replace. \u00a0These certificates had a key length of 512-bits. \u00a0When we upgraded to 5.0 and 5.1, these certificates were maintained. \u00a0As it turns out, this isn&#8217;t compatible with the new VMware Single Sign on service. \u00a0In my case the troubleshooting process led us to reinstall Single Sign On, Inventory service and vCenter 5.1. <\/p>\n<div><a href=\"http:\/\/4.bp.blogspot.com\/-74Q2m16KT5Q\/UG-6SyIXg3I\/AAAAAAAADrM\/WLoZMB1wh8Q\/s1600\/certificate.PNG\" imageanchor=\"1\"><img loading=\"lazy\" border=\"0\" height=\"320\" src=\"http:\/\/4.bp.blogspot.com\/-74Q2m16KT5Q\/UG-6SyIXg3I\/AAAAAAAADrM\/WLoZMB1wh8Q\/s320\/certificate.PNG\" width=\"254\"><\/a><\/div>\n<div>Prior to upgrading, verify the public key length is at least 2048 bits, otherwise replace the certificate.<\/div>\n<p><\/p>\n<div><a href=\"http:\/\/4.bp.blogspot.com\/-CF3odFX0v1U\/UG-6Tby86FI\/AAAAAAAADrQ\/ekTeVV81I64\/s1600\/certificate2.PNG\" imageanchor=\"1\"><img loading=\"lazy\" border=\"0\" height=\"320\" src=\"http:\/\/4.bp.blogspot.com\/-CF3odFX0v1U\/UG-6Tby86FI\/AAAAAAAADrQ\/ekTeVV81I64\/s320\/certificate2.PNG\" width=\"250\"><\/a><\/div>\n<div>If your certificate is the appropriate minimum length, your upgrade should proceed normally and vCenter should function as expected.<\/div>\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>VMware has published information about upgrading to 5.1 and the required length of host certificates. \u00a0In my case, I verified before hand that my certificates were the appropriate length so I proceeded, but as it turns out, my vCenter certificates were not the proper length. Our vCenter was installed first with version 4, which auto-generated [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[55,61,64],"tags":[],"_links":{"self":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts\/331"}],"collection":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/comments?post=331"}],"version-history":[{"count":0,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts\/331\/revisions"}],"wp:attachment":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/media?parent=331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/categories?post=331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/tags?post=331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}