vCenter 5.1 U1 Installation: Part 14 (Log Browser and Web Client SSL)

In this post I cover the basics of replacing the Log Browser and Web Client SSL certificates for vCenter 5.1 Update 1. However, as I’ve mentioned before, VMware has released the vCenter certificate automation tool. That tool automates the replacement of the Log Browser and web client certificates, among others. I now recommend you use that tool instead of manually replacing the certificates. However, you can still follow the instructions below if for some reason the VMware tool doesn’t work for you. You can find the full VMware KB article here.

Since this is the next to last article in the 15-part vCenter 5.1 Update 1 installation series, it’s now time to follow my 4 part certificate replacement series here. The last article in this 15-part series shows you how to replace ESXi host certificates, which the VMware certificate tool will NOT do. You can either jump directly to the SSL replacement tool series and replace all of your vCenter SSL certificates now, or you can go ahead to Part 15 and mint SSL certificates for your ESXi hosts then come back and update the vCenter certificates.

Before we get started, listed below are the other related articles in this series:

Part 1 (SSO Service)
Part 2 (Create vCenter SSL Certificates)
Part 3 (Install vCenter SSO SSL Certificate)
Part 4 (Inventory Service Install)
Part 5 (Inventory Service SSL Certificate)
Part 6 (Create vCenter and VUM Databases) 
Part 7 (Install vCenter Server)
Part 8 (Install Web Client)
Part 9 (Optional SSO Configuration)
Part 10 (Create VUM DSN)
Part 11 (Install VUM)
Part 12 (VUM SSL Configuration)
Part 13 (VUM Configuration)
Part 14 (Web Client and Log Browser SSL)
Part 15 (ESXi Host SSL Certificate)

UPDATE 5/4/2013: Updated content to reflect the recommendation of using the VMware vCenter Certificate automation tool instead of manually replacing the certificates. Updated references to reflect that Update 1 is now out.

UPDATE 11/20/2012: VMware has updated the KB article here with additional information if you are subordinate CAs. Since my lab consists of only a single CA, I don’t cover the subordinate CA steps below. Refer to the KB article for more details.

Log Browser and Web Client SSL Certificate Replacement

1. Stop the VMware vSphere Web Client service and the VMware Log Browser service.

2. From your D:\Certs\WebClient directory copy rui.crt, rui.key and rui.pfx to the directory below.

C:\ProgramData\VMware\vSphere web client\ssl

3. From your D:\Certs\LogBrowser directory copy rui.crt, rui.key and rui.pfx to the directory below.

C:\Program Files\VMware\Infrastructure\vSphereWebClient\logbrowser\conf

4. To un-register the Web Client with the SSO service, open an elevated command prompt and type:

set JAVA_HOME=c:\Program Files\VMware\Infrastructure\JRE

cd /d C:\Program Files\VMware\Infrastructure\vSphereWebClient\SsoRegTool

regTool.cmd unregisterService -si “C:\Program Files\VMware\Infrastructure\vSphereWebClient\serviceId” -d https://SSOServer.domain:7444/lookupservice/sdk -u admin@System-Domain -p YourPassword


5. To Register the service type the command below. Note: The directory paths appear to be case sensitive, so make sure they match exactly what your system has. In particular, the “ssl” directory may need to be in all lower case.

regTool.cmd registerService –cert “C:\ProgramData\VMware\vSphere Web Client\ssl” –ls-url https://SSOServer.domain:7444/lookupservice/sdk –username admin@System-Domain –password YourPassword –dir “C:\Program Files\VMware\Infrastructure\vSphereWebClient\SsoRegTool\sso_conf” –ip “*.*” –serviceId-file “C:\Program Files\VMware\Infrastructure\vSphereWebClient\serviceId”

If successful you should see something like the following:

6. Navigate to C:\Program Files\VMware\Infrastructure\vSphereWebClient and open the ServiceID file in Notepad. Remove all entries except for the two IDs which were listed from the previous registration step (In my case they were :29 and :30, which I highlighted in yellow).

7. Restart the VMware vSphere Web Client and VMware Log Browser services. Wait a good five minutes for them to initialize.
8. Login to the Web Client (using a vCenter admin account, not the SSO admin account) and at this point you should be able to open the Log Browser without any errors and look at the available logs:
You are almost there….proceed to Part 15 to learn how to replace your ESXi host SSL certificates.
Print Friendly, PDF & Email

Related Posts

17
Leave a Reply

avatar
11 Comment threads
6 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
2 Comment authors
JohnAnonymousFABONTHEWEBDan Cruiceanfernee Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
Terafirma
Guest

If anyone has missed the step to save the password from step 1 I have sent Derek a quick SQL script to pull the CA cert out of the SSO database and I am sure he will update with the needed steps.

Loren
Guest

Interesting. On the VCSA, it appears that the command to update the certificates also updates root-ca cert in the SSO root-trust.jks keystore.

I was able to pull a root-ca cert out of the root-ca.jks file, but it didn’t fix the log browser problem.

Also, on the VCSA, the keytool command requires the ‘-rfc’ parameter to output a plain-text PEM certificate. Otherwise it comes out in binary DER format.

I’m working on a newly deployed VCSA, to see if the cert extracted from the root-trust.jks keystore is different…

Loren
Guest

Ok, this fix works for the VCSA as well. However, I couldn’t find the appropriate self-signed cert anywhere on the system after a successful certificate change. It is very easy to save a copy of the right cert before replacing them with CA-signed certs, though.


cp /etc/ssl/certs/Embedded-SSO-Server-Root-CA.pem /etc/ssl/certs/SSO-STS-Root.pem

Then after replacing the certs, run these commands to update the logbrowser.properties file and restart the service.


sed -i.bak ‘s/.*sso-certs=.*/sso-certs=\/etc\/ssl\/certs\/SSO-STS-Root.pem/’ /usr/lib/vmware-logbrowser/conf/logbrowser.properties

service vmware-logbrowser restart

I’ll be updating the script I published on the VMware community discussion to handle this. http://communities.vmware.com/message/2124455#2124455

Anonymous
Guest
Anonymous

Hi,
Thanks for all this work!
Unfortunately, I am not able to get the LogBrowser working…even after having loaded the new chain in the STS certificate, I still have the error…
Is the Logbrowser really working for you?

Johan
Guest
Johan

Hi Derek, Perfect job, I have done every step en the new vCenter is running like a charm.
I only have trouble with the logbrowser (the unregister part at step 4) for some strange reason it keeps saying:
The system cannot find the path specified.
3
I tried everything, even editing the command file, with no result. Filename is correct, capital letters are correct, but nothing works.
Have you got any idea?

Anonymous
Guest
Anonymous

I see Auto Deploy uses certs as well. Can I use the same steps to get those self signed?

Regards

Dan Cruice
Guest

This comment has been removed by the author.

FABONTHEWEB
Guest

I was able to install the web client by renaming the SSL to ssl in C:\ProgramData\VMware then i turned off all vmware services except the sso service, run install again. At one point it asked to overight the certificate and i accepted.

Anonymous
Guest
Anonymous

Hello, i had also trouble with intermediate ca and i have find a solution for my problem. problem: If you try to open the Log-Browser in vSphere Web Client you get the following error: faultCode:Server.Processing faultString:’javax.servlet.ServletException : java.lang.Exception: https://BLPKVSPHERE01.BLPK2000.blpk.ch:12443/vmwb/logbrowser: Unauthorized access‘ faultDetail:’null’ have a look at the logs from Log-Browser under the following directory: C:\Program Files\VMware\Infrastructure\vSphereWebClient\logbrowser\log in my case the following error occurred: 2013-02-06 16:40:22,468 INFO [com.vmware.vide.ws.sso.SsoRequestHandler] [WrapperStartStopAppMain] Using certificate file C:\ProgramData/VMware/SSL/ca_certificates.crt2013-02-06 16:40:22,478 ERROR [com.vmware.vide.ws.sso.SsoRequestHandler] [WrapperStartStopAppMain] Unable to load certificatesjava.security.cert.CertificateException: java.io.IOException: DerInputStream.getLength(): lengthTag=127, too big. solution: – be sure the steps 1 to 8 of Part 14 are well done… Read more »

Anonymous
Guest
Anonymous

Hi DerekMany thanks for the work, it does simplify a lot of work compared to VMware documentation. However, I have run into a problem with Log Viewer as others commented earlier; the error is in the form of: faultCode:Server.Processing faultString:’javax.servlet.ServletException : java.lang.Exception: https://VCENTER-SERVER.DOMAIN.LOCAL:12443/vmwb/logbrowser: Unauthorized access ‘ faultDetail:’null’ I followed the steps as below: 1. Install the SSO Component as per your article and other best practices (including preparations of a SSL Certificate Template on a “Single” Windows 2008 R2 “Enterprise” Root CA and a seperate SQL 2008 R2 database server) 2. Followed by your article:VMware vCenter 5.1 Installation: Part 2… Read more »

Anonymous
Guest
Anonymous

Hi Derek, I have managed to resolve the issue; I came across this blog http://jackstromberg.com/tag/vcenter/ and followed the steps as below and that has resolved the problem: 1. Stop the VMware Log Browser service2. Navigate to C:\Program Files\VMware\Infrastructure\vSphereWebClient\logbrowser\conf via Windows Explorer3. Backup existing rui.crt, rui.key, rui.pfx.4. Replace the rui.crt, rui.key, rui.pfx files with the ones from C:\certs\LogBrowser5. Next, create a new java keystore with the chain trust for the certificate1. Open up an elevated command prompt2. Change directories to the VMware JREcd /d C:\Program Files\VMware\Infrastructure\jre\bin3. Generate the new keystore (Do not change the testpassword or changeit password) (Change the Paths… Read more »

John
Guest
John

Wow! It worked, actually better than doing it manually.
I had a brief moment of panic when I logged into my vCenter server using the vSphere client and the cert showed as "Default vCenter Certificate". Logging into the web client I saw the RSA chain and remembered from the original guide that I needed a restart.

Restarted the vCenter server and everything is working correctly.

You nailed it again Derek! I was thoroughly impressed with the original guide (and remember spending hours manually replacing certificates) and am impressed again with this update.

Thanks man.

Scroll to Top