01 Jun 2010

Replace SSL Certificates: Step 1: Prepare OpenSSL and Microsoft CS

This article forms part of the Replacing vSphere SSL Certificates series.

In order to request and self sign new SSL certificates for VMware vCenter Server 4.x and VMware Update Manager we will need to get a certificate authority up and running. For this lab, we will use a Microsoft Windows 2003 Server running Microsoft Certificate Services as our Certificate Authority. Although we will be using Microsoft Certificate Services to sign the new SSL Certificates, OpenSSL will be used to generate the SSL Certificate Requests that will be submitted to the Microsoft Certificate Authority.

To build the SSL CA Server we will need to have the following software components:

  • A Windows 2003 Server
  • Microsoft Internet Information Services (IIS) enabled
  • Microsoft Certificate Services Installed
  • Visual C++ Redistibutable (Download this from here )
  • Win32 OpenSSL V1.0.0 Lite (Download this from here) 

For this example I have prepared a Windows 2003 Server called LABSSL01 and I've also added the server to the LABS.UK.VIRTUALVCP.COM domain. So, the FQDN of our SSL Certificate Authority server for this example will be: labssl01.labs.uk.virtualvcp.com.

Preparing the server for Microsoft Certificate Services

The first thing that we will need to get in place is IIS. We will use IIS to access the Microsoft Certificate Services Web Portal. The web portal will be handy to:

  • Submit new SSL Certificate Requests to the Microsoft CA
  • Download the signed SSL Certificates
  • Download the CA Root Certificate to client machines

We will be installing the IIS and Certificate Services components at the same time.

Using Add or Remove Programs from the Windows Control Panel, Click the Add/Remove Windows Components Button:

addremove_win_comp_button

Select "Application Server" and click "Details". Then select the following components under "Application Server"

  • Application Server Console
  • Enable network COM+ access
  • Internet Information Services

 iis_comp_selection

Once the components have been selected, Click OK.

With the IIS components now selected, we can go ahead and select the Certificate Services components as well.

Select "Certificate Services", then click "Details"

CA-Details_Button

The Certificate Services components dialog opens. Select the following components before clicking "OK":

  • Certificate Services CA
  • Certificate Services Web Enrollment Support

CA_Component_selection

When Certificate Services CA is selected, the following message will appear. Click "Yes" to continue

CA_Domain_Warning

Now that both IIS and Certificate Services components have been selected, click "Next".

CA-IIS-ClickNext

As we are installing a new Certificate Authority, we need to provide some information for the new Certificate Authority.

For the CA type, select "Stand-alone root CA" and click "Next" 

CA-Type

Now it's time to supply information that will identify the new Certificate Authority. The information provided here will also be included in each SSL certificate that the new CA will sign in the future.

At least the "Common Name for this CA" field should be completed as well as the "Validity period" field.

CA-ID-Info

At the Certificate Database Settings dialog, keep the default settings and click "Next"

CA-DB-Settings

A message will appear stating that in order to complete the installation, Internet Information Services must be restarted. Click "Yes" to acknowledge this message.

CA-IIS-restart

You may also be presented with a message requesting that ASP be enabled. Click "Yes" to enable ASP now.

CA-Enable-ASP

During the installation, you may be prompted for the Windows 2003 Installation CD. Please make sure that you have this handy in order to complete the installation of IIS and Certificate Services.

When the above steps have been completed, your server will be an ASP Web Server as well as a Certificate Authority capable of signing new SSL Certificates. However we will still need to install OpenSSL for Windows. OpenSSL is used to generate new SSL Certificate requests that will be submitted to the new Microsoft Certificate Authority. In this example, our Certificate Authority is called "VirtualVCP SelfSign Certificate Authority"

 

 In order for your client machines to verify the authenticity of any certificates signed by your new CA, you will have to download and install the CA root certificate on each client machine. The new CA root certificate can be downloaded from http://<your-ca-server>/certserv


Installing Win32 OpenSSL V1.0.0 Lite

NOTE: Before installing Win32 OpenSSL V1.0.0 Lite, please download and install Visual C++ Redistibutable from the Microsoft Website.

Download Win32 OpenSSL V1.0.0 Lite from here

Run the Win32 OpenSSL Light installer. At the Welcome dialog, click “Next”

openssl_01_welcome

Select “I accept the agreement” and click “Next”

openssl_02_eula

Keep the default Destination Location as “C:\OpenSSL-Win32” and click “Next”

openssl_03_install_dest

Select "The OpenSSL binaries (/bin) directory" and click "Next"

openssl_05_libdir

Click "Finish" to complete the installation

openssl_06_finish

This then completes the SSL Server preparation. However, as we will be issuing new SSL certificates using the SSL Certificate Authority installed on this server, we will have to import the CA's root certificate into the Trusted Root Certification Authorities store of each of the client computers that will be using the vSphere client to connect to vCenter and VUM.


Continue to the next step: Generate a new SSL Certificate Request

Written by  0 comment
Last modified on Tuesday, 06 July 2010 17:32
Rate this item
(0 votes)

Comments (0)

There are no comments posted here yet

Leave your comments

Posting comment as a guest. Sign up or login to your account.
0 Characters
Attachments (0 / 3)
Share Your Location

@martinclarkson I know. That kinda sucks though. All good things must eventually come to an end.
Follow Rynardt Spies on Twitter