Connectivity Guide Secure Opc Ua Tunneling With Kepserverex: January 2020 Ref. 1.04
Connectivity Guide Secure Opc Ua Tunneling With Kepserverex: January 2020 Ref. 1.04
January 2020
Ref. 1.04
2. Getting Started
This document does not cover the installation and licensing of KEPServerEX. For
instructions, visit the Resource Library and Licensing pages on www.kepware.com.
The OPC UA server is the instance of KEPServerEX where the data sources reside. These
data sources can be PLCs, databases, or other OPC servers where the data is accessed using
communication drivers with KEPServerEX. This instance is typically installed on the controls
side of the network.
The OPC UA client is the instance of KEPServerEX on the other end of the tunnel or on the
enterprise side of the network. This is where other OPC clients, both OPC DA and OPC UA,
access KEPServerEX or where KEPServerEX publishes data to the cloud using the IOT
Gateway or Splunk.
3. Firewall
OPC UA does not use unsolicited callbacks, making it “firewall friendly”. This document does
not include firewall configuration. Organizations have their own security policies dictating
firewall configuration, which should be as secure as possible. For this exercise, please
ensure external client applications can securely access the server instance with a TCP
connection using the port configured in the steps below.
4. Certificates
When a secure OPC UA connection is attempted, a certificate exchange between the client
and the server occurs. This certificate is validated and used for signing and encrypting the
payload. This document makes use of the pre-loaded self-signed certificate created during
the installation process and should be used ONLY for testing and proof-of-concept work. In
KEPServerEX Version 6.7 and higher, this self-signed certificate is valid for three years and
must be managed by the user.
3. Select the default endpoint created during the install for non-local connections. This
endpoint can be identified by having a PC name or IP in the endpoint URL.
4. Select Edit.
5. Choose the correct network from the Network Adapter drop down.
6. For the most secure connection possible, ensure that only Basic256Sha256 security
policy is checked.
7. Make note of the port number so that it can be added to the firewall.
For increased security, change the port number to something other than 49320.
10. Apply the changes to the server Runtime by right-clicking on the Administration icon
and selecting Reinitialize.
41. Channel configuration is complete. All settings can be adjusted by right-clicking on the
channel and selecting Properties.
46. Accept the defaults for Lifetime Count and Keep-Alive Count by clicking Next.
47. Accept the defaults for Max. Notifications per Publish by clicking Next.
48. Set the Sample Interval to half the Publish Rate to ensure no updates are missed. The
Sample Interval is the rate at which the server polls the data source (default is 500 ms).
8.2 Verification
The items added in the OPC UA Client can be viewed by a local OPC DA client.
To verify connection and data flow, follow these steps:
66. From the KEPServerEX Configuration, select Tools | Launch OPC Quick Client. A
connection to the local OPC DA server is established and items should populate the
Detail View pane.
67. Browse for the items in the OPC UA Client group and verify that the data quality is
“Good” and values are updating as expected.