Using TeamPulse with https

TeamPulse can be exposed over https but before that can be done, some configuration changes need to be made. Setting up https involves two main steps: configuring the TeamPulse IIS website and modifying the TeamPulse web.config file.

After configuring TeamPulse IIS settings you can use the TeamPulse Uri Changer in order to automatically change the setting in the web.config file. You just need to download the program and fill in the information and everything will be changed automatically. If you prefer you can follow the following steps:

Step 1: Enabling SSL in IIS 7

The first step to running TeamPulse on https is to configure the TeamPulse website to use SSL.  To do this, log in to the TeamPulse web server, open IIS Manager, and then following the steps in the tutorial entitled How to Set Up SSL on IIS 7.

Step 2: Modifying the TeamPulse web.config

If you plan to always access TeamPulse over https and you don't need the regular http address to work anymore, then you need to make three simple changes:

1. Change the security mode of the basicHttp binding configuration from None to Transport.
2. Change the security mode of the basicRss binding configuration to Transport.
3. Change the security mode of the basicWeb binding configuration to Transport.
4. Replace all instances of httpGetEnabled="true" with httpsGetEnabled="true".

<binding name="basicRss" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:05:00" sendTimeout="00:01:00" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647">
    <security mode="Transport" />
</binding>

To see an example of a web.config file that has these changes made to it, download the related zip file below and review the file named Web-https-only.config.

If you plan to access TeamPulse over both http and https, then a different set of changes needs to be made.  To see an example of a web.config file that has these changes made to it, download the related zip file below and review the file named Web-https-and-http.config.  The changes made to this config file will add new endpoints for all the TeamPulse services and configure the endpoints to use Transport security.  The default TeamPulse endpoints are left untouched.

Note: If your certificate is not valid you should add the following section in the web.config.

<system.net>
    <settings>
      <servicePointManager
          checkCertificateName="false"
          checkCertificateRevocationList="false"
      />
    </settings>
  </system.net>

Note: Please note that at this time the TeamPulse installer will not remember and/or automatically re-apply any customizations made to the TeamPulse website or web.config file.  As a result, any customizations will need to be manually re-applied after any TeamPulse upgrade.

Files