WebNavigator HTTPS Configuration
Once our WebNavigator is configured, we can follow the next practice that we have already done, which involves changing its configuration to access it through a secure and encrypted connection using the HTTPS protocol.
The first step is to go to the Internet Information Services (IIS) Manager, which can be accessed from Administrative Tools or by going to Start -> search programs and files, and searching for "IIS".
The next step is to create a new self-signed certificate. To do this, we locate the PC name followed by the logged-in user, in this case PC (PC\Admin), once selected, we look within IIS -> Server Certificates.
Within the Server Certificates, we will observe the ones that have already been created and we will create a new one.
We assign a name that interests us, and with that, we have generated our certificate.
The next thing we do is go to the site that interests us, in this case to WebNavigator, and on the right side of actions, Modify site -> Bindings. By default, we will see that the HTTP protocol is assigned to port 80 unless another port was configured when running the Web Configurator.
We will add a new one, selecting the type HTTPS, the port that interests us, by default port 443 is the default port for this protocol, and we select the certificate we just created.
Finally, what we are going to configure is SSL (Secure Sockets Layer), we open its configuration screen and select Require SSL, apply the changes and restart our Web site. With that, we can test that it works correctly.
If we open our Internet Explorer, version 8-9, when connecting, the following screen will appear, we select continue and then a pop-up will appear for us to log in, we enter the necessary credentials configured in WinCC and that's it.
We can now access our WebNavigator via https, if we select the "x" symbol in the address bar, we can see information about the certificate.
On the other hand, if we are using an unsupported version of Internet Explorer for WebNavigator, we can use WinCCViewerRT. Once configured, a Security pop-up will appear, where, as before, we will confirm that we want to access.
And here would be our application, running on https and functioning perfectly.
October 26, 2014
If you liked it or found it useful, share it :-)