1

I have spiceworks running on its own server and another server running Exchange. My company purchased an SSL certificate from The SSL store and I was able to install it just fine on my Exchange server but had no idea how to install it on my spiceworks server since spiceworks uses Apache.

So I went on the hunt for a solution and with much research finally got it all to work. I was surprised how hard it was to find a forum that had exactly what I needed all in one post… so here I am…

  1. Now Spiceworks apparently comes with OpenSSL but its pretty buggy. Best solution is to install Cygwin

Cygwin Installer: http://www.cygwin.com/

When you install Cygwin you will need to tell it to install OpenSSL (don’t worry if you forget, you can install and update packages at any time by re-running the setup program, when you get to the package list stage search for OpenSSL and set it to install)

  1. Now since I had already generated a certificate for my Exchange server, all I had to do was export that certificate into a .pfx format and copy that over to my spiceworks server.

From Default Web Site Properties, select the Directory Security tab and then click Server Certificate.

In the wizard, select “Export the current certificate to a .pfx file”.

Enter a filename and then, on the next page, set a password.

Now you will need to separate this PFX archive in to two PEM files. How?

The .pem format is known as base64 encoded X509. Open up Cygwin and here is what you should enter in the prompt and what should be displayed afterwards if everything is going like it should. In this case, replace cert_and_key.pfx with whatever you named your file in the previous step.

openssl pkcs12 -in cert_and_key.pfx -nocerts -out ssl-private-key.pem -nodes
Enter Import Password:
MAC verified OK

openssl pkcs12 -in cert_and_key.pfx -clcerts -nokeys -out ssl-cert.pem
Enter Import Password:
MAC verified OK

openssl rsa -in ssl-private-key.pem -out ssl-private-key.pem
writing RSA key

openssl rsa -text -in ssl-private-key.pem

  1. Those .pem files that you just created will be located in C:\cygwin\home\administrator

  2. Go to C:\Program Files\Spiceworks\httpd\ssl

  3. Backup the existing .pem files that are there just in case something goes wrong.

  4. Take the two .pem files you created and paste them into C:\Program Files\Spiceworks\httpd\ssl. They should have the same names as the existing so make sure they are overwrited.

  5. Now we have the SSL certificate installed you need to restart Spiceworks for it to load the new certificate.
    Now when you try to access Spiceworks via HTTPS you will still receive the Certificate error but if you look at the contents of the certificate you should now see that it contains all the details you entered.

  6. When you look at the contents of the Certificate, you should see an “install” button. Hit it and you will be good to go!

Hope this helps someone!

My references:
http://community.spiceworks.com/how_to/show/922
http://community.spiceworks.com/how_to/show/1469

31 Spice ups
2

thx for share

3

Good guide, thanks for sharing.

4

Great, slightly altered method to http://community.spiceworks.com/how_to/show/922-assign-ssl-certificate-from-iis-to-spiceworks-w-existing-cert - Especially if you’re having issues with the built-in OpenSSL. Thanks.

5

This helped another user, and obviously others. Great job!

6

Having an issue writing the RSA key, anyone get a failure at that part as well?

7

Thanks for the information, I see it on http://community.spiceworks.com/how_to/show/922 also

8

Rather old topic, but if you like running behind a reverse proxy, IIS Reverse Proxy method is super easy and let’s you work with .p12 files instead.

In essence, they all accomplish the same, just simply pick your poison.

9

Great job, we’ve been fighting with this for quite a while. I was able to finish this within 15 minutes.

10

AWESOME!!! This post helped me immensely! I now have the Spiceworks portal set up at my organization. It is forward facing yet protected via SSL and our root certificate. These steps even work well with OpenSSL. I did download and install the latest Windows binaries for OpenSSL. I did not use Cygwyn … only because I was being lazy. I’ve been working on this for 24 hours and finally … finally … got this to work within 15 minutes of finding and meticulously following the instructions.

I AM ONE HAPPY IT DIRECTOR thanks to these instructions!!! :slight_smile:

11

Thanks for this write up. Still valid and works today.

One thing to add is where to put the .pfx file after you export it from IIS. That took me a little bit to figure out.

It’s C:\cygwin\home%username% on the machine you’ve installed Cygwin on.

12

Is this still valid for wildcard purchased certificates?

ie need to come off self cert to a wildcard domain cert.

follow the steps as above. On a 2008 server fyi?

Thanks

13

Yes, Chapsuk. just did it for a wild card cert. I installed open ssl on my windows 7 machine and generated the keys before importing them to the spiceworks server. Thanks VDJ.Ness.

14

On oldie but goodie! I found several different solutions for this, but after getting lost in github I opted to use the above for a wildcard certificate.

Keep in mind Corey’s comment above. It made sense after I thought about it, and I am sure the author may have assumed that was intuitive, but you know some of us… your not alone Corey!