Certificate

A certificate, signed by a certificate authority needs to be created and installed on the web server. How this is done differs if the server is accessible from the public internet or not.

Public Facing Web Server

If the web server is public facing then a free certificate can be obtained using Let's Encrypt. Follow the instructions in SSL/TLS using Let's Encrypt

Alternatively you can use any commercial certificate authority. Ex: DigiCert, Entrust, Thawte, etc.

Internal Web Server

If the server is internal then an internal Certificate Authority will be needed.

1. Identify the Certificate Authority (CA) - If you need to setup Microsoft Certificate Services the following link may:

   • Install the Certificate Authority

2. Install the Certificate - Request and install a certificate for the website under which the application will run. See: How to Get a Certificate from an internal CA

   • The certificate must be created for a website (ex: Default Web Site) not the virtual directory for the web application.

   • A Bit length of 2048 is recommended.

   • Select SHA256 for your hash algorithm.

   • See this Microsoft KB article for more information: http://support.microsoft.com/kb/299875

IIS Configuration

Binding

Add an https site binding

1. Select the Website that contains the web application (ex: Sites/Default Web Site)

2. In the Actions pane, click Bindings... 

3. In the Site Bindings dialog click Add...

4. Add https Binding

5. 1. Type: https:

   2. IP Address: All Unassigned

   3. Port: 443

   4. SSL certificate: Select the certification you installed

   5. Click OK

6. Click Close

HTTP Redirect to HTTPS

Use the URL Rewrite module to change incoming HTTP URLs to be HTTPS.

1. Install the URL Rewrite Module for IIS: http://www.iis.net/downloads/microsoft/url-rewrite

2. Require SSL must not be checked for either Default Web Site or for any application (ex: AdamsAdmin, AdamsWeb, AdamsBridge, etc) under that.  You can check the SSL Settings for each to see that it isn’t.

3. IIS Manager must be closed

4. Add a web.config file to the web server's root directory (ex: c:\inetpub\wwwroot) with the below content or the configuration section only if the web.config already exists.  The web server's root directory is typically c:\inetpub\wwwroot even if you have installed Adams web applications on another drive such as e:\inetpub\wwwroot.
   
   

   web.config

   <?xml version="1.0" encoding="UTF-8"?>
   <configuration>
   	<system.webServer>
   		<rewrite>
   			<rules>
   				<rule name="Redirect to HTTPS" enabled="true" stopProcessing="true">
   					<match url="(.*)" />
   					<conditions>
   						<add input="{HTTPS}" pattern="^OFF$" />
   					</conditions>
   					<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="SeeOther" />
   				</rule>
   			</rules>
   		</rewrite>
   	</system.webServer>
   </configuration>

   
   

5. Open IIS Manager

6. Open Default Web Site → URL Rewite

7. Select the "Redirect to HTTPS" rule and verify it is enabled. If not click Enable Rule 

Require SSL/TLS

Require SSL/TLS/HTTPS for all apps.

1. IIS Manager

2. Select Default Web Site

3. Double click on IIS > SSL Settings

4. Check the "Require SSL" box

5. Leave Client certificates set to Ignore

6. Select Apply in the Actions pane

7. Click to select the Default Web Site

8. Click Restart

Service Endpoints (Pre-ADAMS 6.1)

Make it so that web services can or must use HTTPS.

Edit service endpoints in web.config files for Adams Admin and Adams Web

1. Open web.config

2. Find <services>

3. For each endpoint within each <service> do one of:

   1. For HTTPS access only: Edit “Http” in binding value to “Https”.
      
      Ex: “basicHttpBinding” ➔ “basicHttpsBinding”; “mexHttpBinding” ➔ “mexHttpsBinding”
      

   2. For both HTTP and HTTPS access: Add a copy all endpoints with “Http” in binding value and edit value to have Https.
      
      Ex: Copy endpoint line and edit “basicHttpBinding” ➔ “basicHttpsBinding” – Use this if both HTTP and HTTPS will be used.