Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
mr-conwx opened this issue Sep 21, 2020 · 1 comment · Fixed by #1490
Closed

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

mr-conwx opened this issue Sep 21, 2020 · 1 comment · Fixed by #1490
Labels
bug A bug was identified and should be fixed. compliance An issue was found which is not compliant with the OPC UA specification.
Milestone
1.4.367

Comments

@mr-conwx
Copy link

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 mregen added needs investigation question The issue contains a question. After no activity the issue might be closed. labels Oct 1, 2020
@mregen mregen added the compliance An issue was found which is not compliant with the OPC UA specification. label Oct 21, 2020
@mregen mregen removed question The issue contains a question. After no activity the issue might be closed. needs investigation labels Aug 18, 2021
@mregen
Copy link
Contributor

mregen commented Aug 18, 2021

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

@mregen mregen added the bug A bug was identified and should be fixed. label Aug 18, 2021
@mregen mregen mentioned this issue Aug 20, 2021
Merged
mregen added a commit that referenced this issue Aug 20, 2021
@mregen
Improve https clien/server support (#1490)
4a2f13e 
- add support for security header in client/server libs
fixes #1118
@mregen mregen added this to the 1.4.367 milestone Aug 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug A bug was identified and should be fixed. compliance An issue was found which is not compliant with the OPC UA specification.
Projects
None yet
Milestone
1.4.367
Development

Successfully merging a pull request may close this issue.

Improve https protocol support OPCFoundation/UA-.NETStandard
2 participants
@mregen @mr-conwx