Log In
Register
Forum
Topic RSS
13:07, EET
March 26, 2014
Offline
Hi,
Using SDK 4.4.0 for the Client and the Server on the same computer I recently had errors like this when connecting (impossible to connect without restarting):
com.prosysopc.ua.stack.common.ServiceResultException: Bad_UnexpectedError (code=0x80010000, description=”Bad_UnexpectedError (code=0x80010000, description=”com.prosysopc.ua.stack.common.ServiceResultException: Bad_SecurityChecksFailed (code=0x80130000, description=”Signature could not be VERIFIED”)”)”)
at com.prosysopc.ua.stack.transport.tcp.io.TcpConnection$b.run(SourceFile:540)
It’s strange because it happened one day and was reproductible several times even when deleting the PKI folder but today it’s not reproductible… I would like to know what should I do if it happens again to have immediatly the right logs for instance.
My ideas at the moment are:
– as it is related to signature, at the moment I was creating 2 certificates (2048 et 4096 size) but I will now only create the 2048,
– update to the 4.4.2 SDK,
– active TRACE level for the class ChunkAsymmDecryptVerifier
Do you know what could cause this issue or other things that I could already do?
Thanks
15:27, EET
April 3, 2012
Offline
Hi,
Sounds odd. I would assume either it work or not, not like randomly break.
There is at least one edge case with security mode NONE and multiple certs combined with user auth, but I would assume that is not what is used in this case?
2k and 4k certs can apply to multiple security modes, so we would do multiple endpoints for the server. We have at least one such test for the server side.
Do you also set multiple certs for the client side as well?
Our own apps tend to just use a single 2k cert.
1 Guest(s)
