Running SignalR with SSL

With the certificate installed, switching SignalR to start with SSL is as easy as changing the startup URL on both the clients AND StifleR Server, and configuring IIS for secure Dashboard access.


On new and existing StifleR Clients, setting the SSL info is performed within the StifleR.ClientApp.config file which resides in the StifleR Client installation folder:

<add key="StiflerServers" value="https://SERVER.2PSTEST1.LOCAL:1414”/>

SignalR Dashboard URL Configuration

To configure the web page which will consume the SignalR service, change the URL in the file: config.json which is located in the folder: <InstallDir>\StifleR Dashboards\Dashboard Files\assets\config. The value should reflect the https URL for the StifleR Server API as well as the Dashboard web page.

"backendServerUrl": "https://2PINT.2PINT.LOCAL:1414",
"backendLocationServerUrl": "https://2PINT.2PINT.LOCAL:9000/api",

As with all certificates, make sure that the FQDN that exactly matches the certificate name. If the Dashboard is hosted on the local machine, you cannot use 'localhost', NetBiosName, or IP address. Use only the name to which the certificate is assigned.

StifleR Service Endpoint

You'll also need to assign the Dashboards URL to your SSL URL as part of the SignalR startup routine that is used internally in the Stifler Server Service:

<add key="ListenToUrl" value="https://*:1414/" />
<add key="LocationWSListenToUrl" value="https://*:9000/"/>

This binds SignalR to the all IP addresses on Port 1414. You can also specify a specific IP address, but using * is more portable especially if you set the value as part of a shared configuration file.

Last updated