Sunday, 28 April 2013

Multiple IIS websites running HTTPS with one Self-Signed Certificate

This is my first post and a little 101 however useful nonetheless. During development there comes a time when you have more than one website running in IIS that requires a Secure Sockets Layer (SSL). This would seem fairly trivial, no? However there's a distinct lack of material out there documenting the steps to achieve the holy grail of HTTPS secureness in a local set-up. You may have come across the following error during attempts to set this up:

"At least one other site is using the same HTTPS binding and the binding is configured with a different certificate. Are you sure you want to reuse this HTTPS binding and and reassign the other site or sites to use the new certificate?"

With help from a fellow work colleague the configuration was found. I thought I would share this to hopefully aid others in their search. Right, down to the goodness!
  1. Open up IIS and click the IIS server node and select Server Certificates.

  2. Create Self-Signed Certificate... and name it starting with a wildcard (*) and then followed by the domain name. E.g. *.local



  3. Now to secure your website. Select your website and select Bindings. Click Add..., select Type as https and choose the newly created wildcard SSL certificate you created above e.g. *.local. Finally enter the Host name of your website which in my case is project1.local.



  4. Now you only need to repeat step 3 to add more IIS websites that require a SSL. Remember to change the Host name accordingly for each new website.

No comments:

Post a Comment