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.

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

ApplicationConfiguration.SaveToFile() removes "RejectSHA1SignedCertificates" #184

Open
AntoniPancras opened this issue Jun 6, 2019 · 2 comments

Comments

@AntoniPancras
Copy link

AntoniPancras commented Jun 6, 2019

Hi Team,

We are using Opc.Ua.Core.dll and Opc.Ua.Client.dll ( Version 1.4.354 ) in our application . Our application is targeted to .NET framework 4.6. Basically we have upgraded the OPC foundation SDK from Version 1.3.342 to version 1.04.354.

When we try to communicate our OPC UA client application to any OPC UA server with any security mode ( Basic128Rsa15 , Basic 256 ) We are getting the error message
“SHA1 signed certificates are not trusted” .

It works fine with NONE security .

based on the reference OPCFoundation/UA-.NETStandard#306,
We have added below nodes under ‘SecurityConfiguration’ in our configuration file
"RejectSHA1SignedCertificates" with value false
"MinimumCertificateKeySize" with value 1024

But the ApplicationConfiguration.SaveToFile() function removes the node "RejectSHA1SignedCertificates" from the configuration file .
Could you please advice us any solution for this?

Thanks
Antoni

@AntoniPancras
Copy link
Author

Hi Team,
We have debugged the source code of Opc.Ua.Core.dll and identified that the attribute "EmitDefaultValue" is set to 'false' for the property RejectSHA1SignedCertificates ( \Opc.Ua.Core\Schema\ApplicationConfiguration.cs. )

We have changed the attribute 'EmitDefaultValue' to 'true' as shown below

[DataMember(IsRequired = false, EmitDefaultValue = true, Order = 10)]

Now the issue is resolved. We are able to communicate with OPC server with any security policy successfully.

Please let us know your comments on this fix .
Please do let us know any additional testing needs to be done.

Thanks
Antoni

@PrashantDesai
Copy link

Is this problem is resolved in following Nuget package?? It is not working for me

1.4.360.33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants