search

OPCFoundation / UA-.NETStandard

OPC Unified Architecture .NET Standard
Other
1.97k stars 950 forks source link

'OPCUA-SecurityPolicy' header not created in HTTPS connection #1118

Closed mr-conwx closed 3 years ago

mr-conwx commented 4 years ago

According the UA standard, when using HTTPS, the client shall send the HTTP header 'OPCUA-SecurityPolicy' to specify the security policy used. If not specified, the server shall assume security-policy 'None'. The AnsiC stack used by our server implements this behavior , but the .NET client code does not send the required header. When starting a new session, our server therefore assumes that the security-policy is None, and does not sign the client nonce, which in turn triggers an exception in the client library about invalid signature algorithm.

Is it on purpose that this header is not sent? Is there something that I am missing?

mregen commented 3 years ago

Hi @mr-conwx, thats a bug in the .NET https client. Thanks for reporting!