Understanding Milo Bad Security Error #1430
GodlikePenguin
started this conversation in
General
Replies: 2 comments 1 reply
-
This error is because the certificate or certificate chain of the server is not trusted.
I don't think you do, because if that were the case then this stack trace wouldn't be passing through
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Got it, thanks for the quick reply. Out of interest is there any reason the Sun exception isn't translated into something Milo specific? Should it be obvious enough that this is a server certificate trust issue? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I got the following error whilst connecting to the Prosys OPC-UA simulator using Milo. Apologies for the long stack trace but I just wanted to make sure I covered all the unique elements of the stack trace I could see. From my understanding, my client is trying to open a secure channel with the server, and we believe the server certificate has been sent back as part of the message. We decode the server certificate and try to validate it. The DefaultClientCertificateValidator tries to build the server trusted certificate path using our TrustListManager. Somehow trying to build this path results in an exception from the underlying cert path builder. My first guess from the exception would be that our client does not trust the server, but we currently have a "TrustAll" handler so this shouldn't be possible. This certificate has also been accepted by us before, and we manage to connect successfully the next time we try to connect. I'm trying to understand if there are any other reasons that might cause this exception, or if the most likely explanation is a bug in our server certificate handling. For example, could the simulator have sent back an invalid certificate that was still able to be decoded?
Beta Was this translation helpful? Give feedback.
All reactions