search

Configuring StifleR to use SSL

With the certificate installed, to switch to SSL for SignalR and Dashboard communications, you will need to do the following:

  • Modify the StifleR Server configuration settings.

  • Modify the Dashboard configuration file.

  • Modify the StifleR Client configuration file.

hashtag
StifleR Server Service

You'll also need to modify the SignalR URL and Web Service URLS in the StifleR Server Configuration File:

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

This binds SignalR to 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.

The certificate thumbprint will also need to be added to the StifleR Server Configuration File:

<add key="SignalRCertificateThumbprint" value="thumbprint value"/>
<add key="WebServiceCertificateThumbprint" value="thumbprint value"/>

For the StifleR Server to use any changed settings above, the StifleR Server service must be restarted.

hashtag
StiflelR Dashboard URL Configuration

To configure the web page which will connect to the SignalR service, change the URL in the file StifleR Dashboard Configuration File. The value should reflect the https URLs for the StifleR Server:

    "controller": "https://StifleRServer.domain.com:9000",
    "hub": "https://StifleRServer.domain.com:1414"
circle-info

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.

hashtag
Clients

On new and existing StifleR Clients, the SSL info is set in the StifleR Client Configuration File:

To validate that the client is successfully connecting to the StifleR Server, restart the StifleR Client Service. Check the Event Viewer on the client within:

Applications and Services Logs / TwoPintSoftware / StifleR.ClientApp / SignalR / Operational

There should be an entry for a corresponding event such as:

Connection completed: Server https://StifleRServerName:1414/ Status: RanToCompletion

Last updated