Securing StifleR Operations with SSL

Introduction

This document provides guidance on how to secure StifleR communications with SSL.

Securing StifleR is pretty straightforward, but as with anything involving Microsoft Security and Certificates, you need to get it exactly right or it just won’t play ball.

This document is intended to provide some details around this configuration and hopefully a more coherent description of setting up a certificate for self-hosting SignalR, the communication platform upon which StifleR is built.

What exactly do we need to secure?

A couple of areas of concern:

• SignalR Endpoint Communications - the StifleR Server service that the clients communicate with (default port 1414).

• StifleR Web API - the WebAPI service that the Dashboard connects to (default port 9000).

Note: If the StifleR Server service and the StifleR Dashboard are hosted on separate servers, both servers will need their own certificates.