Can I use secure communication in the BURPVI driver?
From version 16, the BURPVI driver can make use of version 6 of the Automation Net / PVI runtime, where support for secure communication is available.
There are two mechanisms how the communication can be secured: requiring authentication and securing the transport.
When authentication is enabled in Automation Studio and required by the project downloaded on the PLC, the CPU parameters in the BURPVI driver configuration can be extended with the username and password:
/UN=user1 /PW=user1password.
Note: in a next version the BURPVI driver provides an integrated configuration for authentication.
When TLS is enabled in Automation Studio and on the PLC side, depending on the configuration if mutual TLS is configured, the system with the BURPVI driver needs a configuration and corresponding certificate files to also utilize TLS secured communication. In this case the destination port typically is also different. The CPU parameters in the BURPVI driver configuration can be extended with the different target port: /REPO=11179. The configuration file for TLS is also specified in the CPU parameters: /TLS=C:\PLCProject\Physical\Config1\X20CP1684\AccessAndSecurity\TransportLayerSecurity\CClient.sslcfg
In addition the .sslcfg configuration file created in Automation Studio with the corresponding folder structure and file based certificate store needs to be available on the system(s) with the BURPVI driver (Engineering Studio PC for import / Service Engine PC for communication)
In addition the .sslcfg configuration file created in Automation Studio with the corresponding folder structure and file based certificate store needs to be available on the system(s) with the BURPVI driver (Engineering Studio PC for import / Service Engine PC for communication)