Access OPCUA automatic certificate is not created anymore

• Related Articles

• 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) ...

• Secure communication between an OPCUA client and the OPCUA process gateway using a self-signed certificate does not work correctly.

  Summary An OPCUA client can no longer establish a secure connection to the OPCUA server when a self-signed certificate is used. When using an application instance certificate that is signed by a Certifiate Authority, with a matching .crl file in the ...

• The OPCUA server in the process gateway can only access variables from the startup project.

  Summary The OPCUA server in the process gateway is limted to variables of the startup project. The OPCUA server in the process gateway should be enhanced to support multi-project environments. Description The OPCUA server in the process gateway is ...

• OPCUA32: OPC UA Client driver does not connect with username / password anymore if the server does not provide a certificate (e.g. as a nano embedded server)

  Description The attempt to connect to an OPC UA Server with username and password fails when connecting to a server which does not provide a certificate. The error message reads: "Can not validate URI because proper endpoint has no certificate". But ...

• The OPC UA client driver creates an incorrect self-signed certificate

  Summary When a new connection is created in the OPCUA32 client driver a new self signed certificate is automatically created, but the certificate does not contain a SubjectAltname as required for OPC UA application instance certificates. This may ...