Introduction
This article describes how to redirect users accessing the Cireson Portal on an HTTP address to the same address on HTTPS. For example, if the user tries to access the Cireson Portal at http://myserver/incident/edit/IR1234 the user will be redirected to https://myserver/incident/edit/IR1234.
Install URL Rewrite
The first step is to install the URL Rewrite module for Internet Information Services (IIS). This is a supported module provided by Microsoft. You can learn more about URL Rewrite and download it from Microsoft's site here: http://www.iis.net/downloads/microsoft/url-rewrite .
Configure URL Rewrite Rules
Once URL Rewrite is installed you can edit the Cireson Portal web.config file to add the URL Rewrite rules. Open a text editor as an elevated administrator and then open the file C:\inetpub\CiresonPortal\web.config. Search for the element in the file. Just below that element add the following elements.
    <rewrite>
      <rules>
        <rule name="HTTP to HTTPS Redirect" stopProcessing="true">
          <match url="(.*)" />
          <conditions>
            <add input="{HTTPS}" pattern="OFF" />
          </conditions>
          <action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Found" />
        </rule>
      </rules>    Â
    </rewrite>Â
Save the file. Restart the web site.
Important note:Â After each upgrade installation of the Cireson Portal you will need to add these rules again because the web.config file is completely replaced with a new one by the installer.
If changing url to https:// or renaming the url vs just redirecting
If you removed the access to the original HTTP:// site (not just redirecting), simply going to the new URL may not work.
The path to the old url is probably still set in the Portal Admin Settings > Setting Items > AnalystsHomePage & EndUserHomePage
Option 1: If you enter the new url, followed by the ending of the home page url (*/ServiceCatalog/Listings/# or whatever Home page you decided on), this will get you to a working page to enter the new URL in the settings.
Option 2: If you go directly to the Setting Items table in the ServiceManagement db on the SQL Server, you can update there too.
Now your new URL should work.