OPC UA Client SDK (Unified Automation) 2.5.4 Client certificate becomes invalid on computer name change

Question

For OPC UA Client SDK 2.5.4 , on computer name change the client certificates needs to be recreated as they becomes invalid. Why, is it documented anywhere?

In Version 2.0, on computer name change the clients certificates were not affected and hence there was no need of recreating them. Using a Dotnet 4.5 and C# 6 supported application.

Answer 1

In version 2.1.0 change log there is the line

• Replaces DC=localhost in ApplicationCertificate SubjectNames with DC=<computername>

So a certificate with localhost in its SubjectName cannot be found, because certificates with <computername> are searched.

After version 2.1.0 we need to recreate client certificate also along with server certificates, on computer name change.