Log In
Register
Topic RSS
10:52, EEST
April 9, 2013
Offline
Hi,
I am using the latest OPC UA Client (2.3.3-170)
It seems like the ApplicationUri is created at launch of the software.
The problem is that sometimes it does not match the one from the Certificate.
The one in the certificate is like that:
urn:[COMPUTER_NAME].[DOMAIN_NAME]:ProsysOpcUaClient
The one in the CreateSession (the same in the About Menu) is
urn:[COMPUTER_NAME]:ProsysOpcUaClient
When I restart the application sometimes the one in the About Menu/CreateSession is the same as the certificate.
As specified in the OPC UA Specification, the OPC UA Server shall check both when connecting with a secure SecurityPolicy.
So sometimes I can not connect Prosys OPC UA Client with my OPC UA Server with a secure Security Policy, only None is working.
Regards.
Camille
12:23, EEST
April 3, 2012
Offline
Hi,
As the ApplicationUri must be globally unique (at least in the context of the network), the hostname is used for a part of it.
If the computer is moved from a network which has domain to one without (or domain/hostname changes), then currently you need to delete the application certificates and then restart the application so that they are recreated when the application starts. Hopefully in the future we can manage this situation more conveniently.
The certs are in folder C:\ProgramData\Prosys\ProsysOpcUaClient\PKI\CA\private on windows (note that the ProgramData is a hidden folder by default, but copying that to windows explorer should work) and on others OS under (user.home)/.prosys/ProsysOpcUaClient/PKI/CA/private.
– Bjarne
1 Guest(s)
