With version 14.0.4.3 (patch in December), it was claimed that it was possible to switch to HTTPS. Once further problems have been resolved, a version will be released in CW6 that will make this more feasible. The release will be announced in the news block.
For future versions, we will provide faster solutions with less configurations needed.
Preparation by the customer's IT department
The IIS requires a certificate. It is not advisable to use the "Self-Certificate" option, as the "Edge Chrome" and "Chrome" browsers no longer allow this in almost all companies. The only browser that still allows this is Firefox, although this may violate the company's security regulations.
The procurement and integration of the certificate are the responsibility of the customer's IT department. Hexagon and the Application Engineers will not offer any support here.
Settings in the IIS and in the JSON files
The certificate is issued for a specific "name" of the server.
If the web client has not yet been installed, it is recommended to use exactly this address (short name, full name with domain) during setup.
If the web client has already been installed, the addresses in the 5 *.SON files must be adapted:
SSL must be activated in the IIS:
In the Launcher.JSON, the entry "https" must be set to "True". If the entry does not exist (due to an older version) it has to be written in there:
in all *.JSON files of the web products:
the maybe existing entry in "webAdress" must be removed:
