Skip to main content
Skip table of contents

Domain name and HTTPS

Introduction

The following documentation provides a baseline for configuring IIS to handle domain binding and SSL termination.

SSL termination can be implemented via other solution than IIS, but requires the setup of a reverse proxy (such as NGINX) which requires some configuration :

Prerequisites

In your DNS, create or configure a unique subdomain record for the proPilot application, for example :

CODE
propilot.example.com. 3600 IN A 0.0.0.0

IIS configuration

image-20240328-143904.png
  • Set the Host name for the HTTP binding

image-20240328-143817.png
  • Create a new configuration binding to handle HTTPS

image-20240329-100602.png

proPilot configuration

  • Edit the Web.config (C:\Program Files\Deployments Factory\ProPilot\Web.config) file with a text editor

  • Search the rewrite element and add a rule to automatically redirect HTTP to HTTPS

    XML
    <rewrite>
      <rules>
        <rule name="HTTPS Redirect" stopProcessing="true">
          <match url="(.*)" />
          <conditions>
            <add input="{HTTPS}" pattern="^OFF$" />
          </conditions>
          <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" appendQueryString="false" />
        </rule>
        <rule name="Angular Routes" stopProcessing="true">
          <!-- do not change this block -->
        </rule>
      </rules>
    </rewrite>
  • Search the httpCookies element in system.web and edit the domain value

    XML
    <httpCookies domain="propilot.example.com" httpOnlyCookies="true" requireSSL="true" />
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.