Configuring SSL on IIS 7

First install the SSL public/private key certificate into IIS.

Edit the web site bindings to add HTTPS protocol support to the web site:

Add the HTTPS binding, and select the certificate you installed earlier.

Once the HTTPS protocol is added, you can make it mandatory:

Configuring SSL on IIS 6

1.       In IIS Manager, double-click the local computer, and then double-click the Web Sites folder.

2.       Right-click the Web site or file that you want to protect with SSL, and then click Properties.

3.       Under Web site identification click Advanced.

4.       In the Advanced Web site identification box, under Multiple identities for this Web site, verify that the Web site IP address is assigned to port 443, the default port for secure communications, and then click OK. Optionally, to configure more SSL ports for this Web site, click Add under Multiple identities of this Web site, and then click OK.

5.       On the Directory Security or File Security tab, under Secure communications, click Edit.

6.       In the Secure Communications box, select the Require secure channel (SSL) check box.

7.       To enable SSL client certificate authentication and mapping features, select the Enable client certificate mapping check box, click Edit, add the 1-to-1 or many-to-1 mappings you need, and then click OK three times.

Web.config changes

You also need to make changes to the web.config file in the Web installation. You will need to change “binding1” into “bindingHttps” for Web Extensions and Mail Link.

Web Extensions

Change from:

  <!-- Services configuration -->

  <system.serviceModel>

    <services>

      <service name="SuperOffice.TrayApp.Server.TrayApp2Server" behaviorConfiguration="SoWcfBehavior">

        <endpoint binding="basicHttpBinding" bindingConfiguration="binding1" contract="TrayApp2Service" />

      </service>

to:

  <!-- Services configuration -->

  <system.serviceModel>

    <services>

      <service name="SuperOffice.TrayApp.Server.TrayApp2Server" behaviorConfiguration="SoWcfBehavior">

        <endpoint binding="basicHttpBinding" bindingConfiguration="bindingHttps" contract="TrayApp2Service" />

      </service>

Mail Link

Change from:

       <service name="MailLink.Server.MailSuperOffice.MaLinkWcfServer" behaviorConfiguration="SoWcfBehavior">

        <endpoint binding="basicHttpBinding" bindingConfiguration="binding1" contract="MailLinkService" />

      </service>

to:

    <services>

      <service name="MailLink.Server.MailSuperOffice.MaLinkWcfServer" behaviorConfiguration="SoWcfBehavior">

        <endpoint binding="basicHttpBinding" bindingConfiguration="bindingHttps" contract="MailLinkService" />

      </service>

Exposed Webservices

If you are exposing the web-services on the web server, you will also need to map the web services to the new https binding.

<service name="SuperOffice.CRM.Services.WcfService.WcfSoPrincipalService" behaviorConfiguration="SoWcfBehavior">

  <endpoint binding="basicHttpBinding" bindingConfiguration="bindingHttps" contract="WcfPrincipalService" />

  <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>

</service>

Also make sure the httpGetEnabled is set to false:

<behaviors>

      <serviceBehaviors>

        <behavior>

        <serviceMetadata httpGetEnabled="false" />

          <serviceDebug includeExceptionDetailInFaults="true" httpHelpPageEnabled="true" />

          <dataContractSerializer maxItemsInObjectGraph="6553600" />

        </behavior>

      </serviceBehaviors>

    </behaviors>