It appears to be working now with the latest nightly build.
This is the new re-generated cert that works
Ignition OPC UA Client.cer (1.1 KB)
1 Like
Great, thanks for confirming.
I think that is the fastest I have ever seen a bug fixed in a large software suite like Ignition. Very impressive. Now back to the Ignition University courses for me, hopefully Ill have a chance to use this software more in the future.
2 Likes
Hang around! It'll start to feel normal, and your opinion of other brands will plummet.
1 Like
Hi Kevin,
This thread is about three months old, but I the same issue with another OPC UA server. The ignition version is 8.1.28 which I assume had this certificate issue resolved. However in my case, when I disable the certificate validation, it works. Would that be ignition client or the UA server causing the issue? Thank you.
If you can connect after disabling certificate validation then it's not the same issue - it's the Ignition client that is rejecting the server certificate for some reason.
Setting the logger you find searching for "CertificateValidationUtil" and then forcing the connection attempt again (edit/save) might yield some helpful log messages.
It would also be useful if you could upload your server's certificate for me to look at.
Here is the server certificate:
c7d3290359be604aac662625c691cbee4277311a [CN%3DNodeOPCUA-TEST].der (1.1 KB)
One of the logger messages is "certificate path: [CN=NodeOPCUA-TEST,O=NodeOPCUA,L=Paris,ST=IDF,C=FR]",
The are other two messages but they have sensitive information and I cannot share here.
This certificate is not a valid OPC UA certificate because it's missing some of the required keyUsage extensions.
For RSA keys, the keyUsage shall include digitalSignature, nonRepudiation, keyEncipherment and dataEncipherment.
This certificate only has:
I will bring this issue to the vendor attention. Thank you for the help.