The installation still offers the user a choice between a Normal (insecure) and Secure setup and clearly describes the differences between them. However, a secure setup will no longer require users to enable applications. All installed applications will be enabled by default for both the normal and secure setup installations.
As described in the installation itself, after installation, the secure setup will require a login to Workbench, will use HTTPS by default and disable HTTP for remote connections. (HTTP is still used for local connections). The GENESIS64 IIS application pool will be disabled, which will prevent WPF WebHMI clients from connecting. (WPF WebHMI requires Internet Explorer. This restriction does not affect HTML5 WebHMI clients. The functionality can be re-enabled in Workbench, in the Configure Application Setting(s) editor of the project.
In the Normal setup, the security is disabled, and the Security is set to Testing Mode.
Since HTTPS, WS-HTTP and NET.TCP connections will be obsoleted in the future, we recommend using the connection via WebSockets. Secure installation will convert all obsoleted connections to WebSockets (via HTTPS). The communication between the servers and the clients on the same machine is always via HTTP. Using HTTPS on a local machine is not making the machine more secure, ant it actually cause unexpected issues.
For a Normal (insecure) installation, anonymous connections for remote clients are allowed. The user does not need to be authenticated.
With a Secure installation, we disable these connections. It means that only authenticated clients can connect to the server. It is valid e. g. for GraphWorX or Workbench clients. To be able to connect to the Frame WorX server, the clients need to be authenticated via HTTPS authenticated connectivity.
Install Shield Wizard
