Adding SSL Support: v2026.07+

Our TASKE web applications use real-time widgets (based on WebSocket technology) to transmit data. The TASKE Widget Server bridges communication between the real-time widgets in the browser and the TASKE Web Server. If you have secured TASKE web applications with an SSL certificate, then you must also secure the TASKE Widget Server with that same certificate.

This article describes how to add SSL support to the TASKE Widget Server. You must:

  • export the Secure Sockets Layer certificate from Microsoft Internet Information Services (IIS)
  • create the certificate
  • configure the Windows Registry
  • test communications

Before you begin

This article assumes you have secured your TASKE web applications with a Secure Sockets Layer (SSL) certificate. This article only applies to TASKE versions 2026.07 and newer.

You must have a working knowledge of SSL certificates and a familiarity with editing the Windows Registry. If you require assistance, contact TASKE Support.

Export the SSL certificate from Microsoft Internet Information Services

You must export the SSL certificate currently securing your TASKE web applications to a file named mycert.pfx.

Steps

  1. Open IIS on the computer that is running TASKE.
  2. In the IIS Manager, in the left panel, click the computer name.
  3. In the right panel, double-click the Server Certificates icon.
  4. Right-click the certificate and click Export.
  5. Do the following:
    • Browse to your TASKE installation folder. By default, this folder is:
      • C:\Program Files (x86)\TASKE Technology Inc\Contact for TASKE Contact
      • C:\Program Files (x86)\TASKE Technology Inc\Visualizer for TASKE Visualizer
      • C:\Program Files (x86)\TASKE Technology Inc\Essential for TASKE Essential
    • Type the filename mycert.pfx.
    • Type a password.
    • Confirm the password.
    • Click OK.

Convert to PEM Certificate

These steps create a taske.widgets.pem file. The TASKE Widget Service will look for a file with this name by default. This file contains both the private key and the certificate. TASKE ships with the necessary files to convert the file from a pfx to a pem file.

  1. Open a command prompt.
  2. Change to the directory containing mycert.pfx, e.g. CD “C:\Program Files (x86)\TASKE Technology Inc\Contact”
  3. Enter: .\openssl.exe pkcs12 -in mycert.pfx -out taske.widgets.pem -nodes

Configure the Windows Registry

The TASKE default installation creates the initial Windows Registry branch and basic keys to run an unsecured HTTP server.

For information about editing TASKE Registry Keys see this article: Editing TASKE Registry Keys.

Registry Branch

HKEY_LOCAL_MACHINE\SOFTWARE\TASKE Technology\Call Management\Widget Service

Registry Keys

Name: Address

Type: String
Default: 127.0.0.1
Description: The network address or IP. For secured servers this should be a name (for example, machine.example.com).

Name: HTTP

Type: DWORD (32-bit)
Default: 1
Description: Indicates whether the unsecured (HTTP) server is enabled.
Note: Zero (0) means false or disabled. Any other number means enabled.

Name: HTTPS

Type: DWORD (32-bit)
Default: 0
Description: Indicates whether the secured (HTTPS) server is enabled.
Note: Zero (0) means false or disabled. Any other number means enabled.

Name: Port

Type: DWORD (32-bit)
Default: 9002 (decimal)
Description: The network port on which the unsecured server listens for widget connections.

Name: Secure Port

Type: DWORD (32-bit)
Default: 9443 (decimal)
Description: The network port on which the secure server listens for widget connections.

Name: PEM Cert Path

Type: String
Default: taske.widgets.pem
The path to the file that contains the PEM certificate. If just the filename, the server’s path is prepended.

Name: PEM Key Path

Type: String
Default: taske.widgets.pem
Description: The path to the file that contains the PEM certificate key. If just the filename, the server’s path is prepended.

Test communications

When run as a Windows service, the TASKE Widget Server logs errors to the Window Event Viewer. No other visible feedback is provided. If you need to debug issues, follow these steps.

Steps

  1. Ensure that the TASKE Widget Server is not running in TASKE Console.
  2. Open a command prompt and change to the TASKE installation folder.
  3. Type the following and press Enter.
    taske_widget_translator -console
  4. Attempt to sign into TASKE.
    TASKE displays status messages and XML text streaming based on when the widget connections are successful. If you see errors, stop the server and correct the configuration.
  5. When you are finished testing, press CTRL + C to stop processing.

Useful links