OPCUA32: Communication with a specific OPC UA server using username / password for authentication, does not work

OPCUA32: Communication with a specific OPC UA server using username / password for authentication, does not work

Description

The OPCUA32 OPC UA client driver cannot communicate correctly with an OPC UA Server requiring authentication using username/password under specific circumstances. The OPC UA client incorrectly sends password in plain text whereas the OPC UA server expected an encrypted password without specifically asking for the password to be encrypted. 
To allow communication in these circumstances: 
  • Update to the latest build of zenon 8.20, 10 or 11.  


Item ID: 252224
Version: 10.00 Build: 100998
Version: 8.20 Build: 102334

    • Related Articles

    • FAQ: How can I browse an OPC UA Server using the zenon OPC UA Client Driver?

      Go to Drivers > New Driver Create a Driver of Type "OPC UA Client Driver" Open the Driver Configuration Go to "Connections" Create a new Connection Enter your Discovery URL Enter your Server URL manually or click the 3 dots to browse the Discovery ...

    • OPC-UA Server: DNS Name used in certificate created by zenon.

      The creation of the DNS name in the OPC-UA Server certificate may vary depending on the zenon build and if the machine is within a Workgroup or is part of a Domain. This information can be verified in the certificate, the certificates files (*.der) ...

    • Checklist: Communication to TwinCat via BeckhoffNG driver

      Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. TwinCAT ADS communication library ...

    • Checklist: Driver(s) cannot establish a reliable communication

      Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • Checklist: Smart Client cannot establish a reliable communication

      Time estimate: 60 minutes Please go through all the items in the following checklist. If necessary, confirm any information you cannot verify with the IT department before contacting your local COPA-DATA representative. Checklist usage: #. [Quick ...