Wednesday, August 6, 2008

How To SSL-Enable a Web Application

I've seen many posts around the topic of SSL-enabling a Web Application and how many go through the process of Extending the Web Application to do so. While this does work, it is not necessary. Extending a Web Application should really be used when you want to offer a different authentication mechanism than the default one. To SSL-enable a Web Application all you need to do is (1) add an Alternate Access Mapping entry and (2) install the SSL certificate on the web site. To add a new AAM entry perform the following steps:


  1. From the Central Administration home page navigate through Operations --> Alternate Access Mappings (under the Global Configuration section)

  2. In the Alternate Access Mapping Collection dropdown (near upper-right) select Change Alternate Access Mapping Collection

  3. In the Select An Alternate Access Mapping Collection page select the relevant Web Application Name you want to create a new entry for

  4. In the Alternate Access Mappings page click the Edit Public URLs button near the upper-left.

  5. Enter the desired URL in one of the 4 Zones available then click the button

  6. Install the SSL certificate to the relevant IIS website

At this point you should be good to go!


- M


3 comments:

Anonymous said...

Thanks Michael. Is this the approach to take if you want to have two URLs for the same site collection, one secured and one unsecured?

Michael Mukalian said...

That's actually a little different Tim and I want to make sure I understand the question correctly. If you are speaking of "secure" in terms of http and https, then yes this is how I approach that. If you are speaking in terms of authentication (AD vs. Forms) then no. For different authentication modes you should Extend the Web Application.

- M

Anonymous said...

Thanks again Michael. I was thinking of the former - same AD authentication, but one URL via HTTP and the other HTTPS.