Sections Where HTTPS Is Used

Sections Where HTTPS Is Used

In Wise SCADA, TLS-protected connections can be established using the HTTPS, WebSocket Secure, and Wise SCADA Secure options. These options are configured in different sections and require the generation of a server certificate.

Pages

The protocol over which the HTML pages created in the Pages section will be published can be determined.
One of the HTTP or HTTPS options can be used from the Protocol field.

  • Default TCP port for HTTP: 80
  • Default TCP port for HTTPS: 443

For example, if HTTPS is selected and the default port 443 is used, the access address for a page could be as follows:
https://192.168.0.104/Page.html
And when HTTP is used:
http://192.168.0.104:443/Page.html

Servers

In the Servers section, secure HTTPS equivalents of HTTP-based server protocols can be used.
For example, the following protocols can be run over HTTPS:

  • HTTPS: JSON
  • HTTPS: XML
  • HTTPS: Plaintext

While HTTP versions use unencrypted connections, HTTPS versions perform communication between the client and SCADA over TLS.
For example, by selecting HTTPS: JSON instead of HTTP: JSON, the JSON-based service can be made to broadcast over HTTPS.

Additionally, the WebSocket Secure and Wise SCADA Secure protocols can be used in the Servers section.
WebSocket Secure protects WebSocket communication with TLS. Wise SCADA Secure, on the other hand, performs data exchange between two Wise SCADA projects over a TLS-protected connection.
These protocols use different communication methods than HTTPS services; however, the steps for generating a certificate and installing it on the client are common.

Clients

In the Clients section, a secure connection option is available for WebSocket communication.

  • WebSocket
  • WebSocket Secure

WebSocket refers to the standard WebSocket connection, while WebSocket Secure refers to the secure WebSocket connection protected by TLS.

  • WebSocket : ws://
  • WebSocket Secure : wss://

WebSocket Secure should be used in cases where secure network communication is required.

The following protocols can be used in the Clients section to connect to another Wise SCADA server:

  • Wise SCADA
  • Wise SCADA Secure
  • WebSocket
  • WebSocket Secure

Wise SCADA is the native communication protocol used for data exchange between two Wise SCADA projects. Wise SCADA Secure performs this communication over a TLS-protected connection.

WebSocket refers to the standard WebSocket connection, while WebSocket Secure refers to the TLS-protected WebSocket connection. The ws:// prefix is used in WebSocket addresses, and the wss:// prefix is used in WebSocket Secure addresses.

The protocol selected on the client’s Clients page must be the same as the protocol selected on the server’s Servers page. The server’s address and the port number defined in the server configuration must be entered in the Server Addresses field.

A server certificate must be generated before using Wise SCADA Secure or WebSocket Secure. The server IP address or hostname used in the connection must match one of the addresses defined in the certificate.

If connecting from another computer, the WiseSCADA.cer file located in the server project’s Certificate folder must be installed in the Trusted Root Certification Authorities store of the client computer.

Important: Since the WiseSCADA.pfx file contains private key information, it must not be distributed to client computers. WiseSCADA.cer must be used for client installation.
For steps on generating a certificate and installing it on a client computer, please refer to the Certificate Generation and Certificate Installation sections on the HTTPS page.

Web Servers

The protocol over which the Web Server will broadcast can be selected in the Web Servers section.
Available protocols:

  • HTTP
  • HTTPS

When HTTPS is selected, Web Server connections are established over HTTPS, and the corresponding certificate is used.

Example:
https://192.168.0.104/Screen.html

TCP Port and URL Generation

On Web Server pages, the URL information is automatically generated based on the protocol used and the TCP port.
If the default port is used, there is no need to specify the port number in the URL.

For example:
HTTP / Port 80
http://127.0.0.1/Screen.html
HTTPS / Port 443
https://127.0.0.1/Screen.html

However, when a port other than the default is used, the port number is shown in the URL. For example, if the TCP Port is set to 8443 for HTTPS:
https://127.0.0.1:8443/Screen.html

Similarly, if the HTTPS protocol is selected but the TCP Port is set to 80: It will be displayed as
https://127.0.0.1:80/Screen.html.
This address can also be checked via the tooltip displayed over the URL field on the page in the Web Servers section.

Note: Whether the port number is shown in the URL does not depend on the use of HTTPS, but rather on whether the default port for the protocol is used.

Leave a Reply