OPCUA Server - Segmentation Fault when client authenticates using non-existent certificate

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

• FAQ: What are Installation and Security considerations of the zenon Smart Server and Smart Client?

  The attached document (English only) describes in some detail the specifics of the zenon Smart Server Application and the zenon Smart Client Application. Also a short explanation of security features and components is given. More information about ...

• Checklist: Client/Standby cannot establish a reliable connection with Service Engine Server

  Time estimate: 45 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] ...

• MQTT - segmentation fault when the you connect to a brocker with bad certificate.

  Description In the Logic Service, if a connection to a broker with an invalid certificate is established, the Logic Service is terminated unexpectedly with a segmentation fault. This bug has been fixed. The Logic Service is no longer terminated ...