Use Google Chrome to access FairCom browser-based tools. Other browsers may cause unexpected behavior.
FairCom servers include a built-in app server that supports FairCom’s JSON APIs, browser-based applications, and MQTT broker. The app server communicates over TCP/IP ports using HTTPS, WebSocket, and MQTT protocols.
You enable and configure listeners for these ports and protocols in the services.json file. You must use different ports for TLS and non-TLS connections. For TLS connections, configure the "tls" property for a listener, such as the following HTTPS configuration.
{
"serviceName": "https8443",
"description": "Port 8443 using TLS-secured HTTPS protocol",
"port": 8443,
"protocol": "https",
"enabled": true,
"tls": {
"certificateFilename": "server.crt",
"privateKeyFilename": "server.key",
"certificateAuthoritiesFilename": "ca.crt",
"allowedCipherSuites": "AES256-SHA256"
}
}You can run the
nmapcommand line utility against FairCom's default app server port 8443 to verify the TLS ciphers in use. Linux includesnmapand you can installnmapon Windows and MacOS.
nmap-p 8443 -v -Pn --script ssl-enum-ciphers localhost
Using TLS with FairCom's browser-based apps
On the machine that Google Chrome is running on, install your private CA certificate into the OS keystore.
Then, install a server certificate (signed by that CA) into the FairCom server that Google Chrome is talking to by following these steps. The "target" of these steps is the "https8443" block of the "listeners" array in "services.json".