Part 1: Generate and install self-signed certificate for testing (optional)
Note: This step may be skipped if the user has a supplied key that Is already configured and verified to be working.
- Download precompiled Binaries for openSSH if they are not on your system. Windows users may want to use the following URL: https://wiki.openssl.org/index.php/Binaries
- Generate a key and cert file using the following command:
openssl.exe req -x509 -newkey rsa:2048 -keyout -out -days 365 –nodes
Note: For illustrative purposes, when it asks for FQDN or name, a development machine accessible using the URL matthew-win8.ts3d.lan is used. This will mean that the certificate will work with URLs in the form of ws://matthew-win8.ts3d.lan:<port_num>. We had our IT person create a DNS entry for our developer machine.
- To install the cert in chrome (this will also enable the cert in IE/edge) perform the following steps:
- Go to Settings
- Show advanced settings…
- Click on Manage certificates under HTTPS/SSL
- Click ‘the Trusted Root Certification Authorities’ Tab
- Click on Import button and select the certificate that was generated above
- After the certificate is installed, the browser will need to be restarted.
Part 2: Configuring HOOPS Communicator Server to server Secure Websocket data
- Launch the settings builder application and chose the mode you desire to configure.
- When prompted if IP’s should appear in addresses type: no
- When prompted if you need to configure SSL type: yes
- When prompted, specify the paths to your key and certificate files.
Reboot the browser after I installed the certificate.