# Securing StifleR operations with SSL

## Introduction

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

Securing StifleR is 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 provides details around security configuration and describes the process of setting up a certificate for self-hosting SignalR, the communication platform upon which StifleR is built.

### What exactly do we need to secure?

There are two components that must be secured:

* **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).

{% hint style="info" %}
Note: If the StifleR Server service and the StifleR Dashboard are hosted on separate servers, both servers will need their own certificates. 
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.2pintsoftware.com/stifler/configuration/securing-stifler-operations-with-ssl.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.