Hi,

Sorry! EDIT on last post; The local OPC server also doesn't work all the time. Sometimes the client doesn't connect to that server as well. The exceptions are;

Self Signed Certificate is not trusted. IssuerName: CN=MHWirth Reference Server, C=US, S=Arizona, O=OPC Foundation, DC=eurw157325

and

Certificate is not trusted. SubjectName: CN=DE.RuntimeService, DC=EURW157325 IssuerName: CN=DE.RuntimeService, DC=EURW157325


Best,
Ahmad

Hi again,

One more thing I probably need to say is that I have another OPC server running locally (with Security Policy: None, Security Mode: None and Anonymous authentication) and I connect to that with no problem, but when I try to connect to the customer Siemense server which is (Security Policy: Basic256Sha256, Security Mode: Sign & Encrypt and with Username/password authentication type) I get the issue that was explained in the previous posts.

Just thought this information might come handy.

Best,
Ahmad

Hi,

This is client machine (i.e. my local PC that I am running the client on)

Best,
Ahmad

Hi and thanks for your reply.

Yes, that's right. The server Url does not start with Https.
To answer your questions;
1- I am not very familiar with the server as it's a third party server that our customer provided. The customer said it's available via Internet and we can access it with the username/password that he has created for us. If you get the user/pass you will be able to connect to the server as well, but I'll have to check that with them.

2- I deleted OPCFoundation folder in ProgramData on my local pc (the development environment is my local pc) to make sure leftover certs from before is not there, then I ran the client and I didn't get the "Cerificate chain not complete" anymore but I got the error "Self Signed Certificate is not trusted. IssuerName: CN=DE.RuntimeService, DC=EURW157325". I have not configured EasyUAClient to use specific certificates. The following is what I have configured in my c# code;
{
EasyUAClient.SharedParameters.EngineParameters.CertificateAcceptancePolicy.AcceptAnyCertificate = true;
_client.Isolated = true;
_client.IsolatedParameters.SessionParameters.KeepAliveInterval = 2000;
_client.IsolatedParameters.SessionParameters.EndpointSelectionPolicy.AllowedMessageSecurityModes = UAMessageSecurityModes.SecuritySignAndEncrypt;
_client.IsolatedParameters.SessionParameters.EndpointSelectionPolicy.SecurityPolicyDisplayName = "Basic256Sha256";
_client.IsolatedParameters.SessionParameters.EndpointSelectionPolicy.MessageSecurityPreference = Sign.Positive;
_client.IsolatedParameters.SessionParameters.UserIdentity.UserNameTokenInfo.UserName = "MHWirth";
_client.IsolatedParameters.SessionParameters.UserIdentity.UserNameTokenInfo.Password = "*****";
}

3- This is the client server, I don't think the server has been set to trust my client. However when I connect to the server with UaExpert, it gives the two pop-ups attached. First untrusted certificates that when we say continue trusting for this session, it gives the second pop-up with BadCertificateHostNameInvalid during CreateSession" in UaExpert. When I press "ignore", it connects to the server. So should I ask the customer to configure his server to trust the client?

Best,
Ahmad

Hi,

I am implementing OPC UA clientin C# (with .Net framework 4.7.2) using Quick OPC sdk (EasyUA client). When trying to connect to a Siemence OpcUa server, it throws this exception: OPC UA service result - {BadSecurityChecksFailed}. An error occurred verifying security. --> {BadSecurityChecksFailed}. Certificate chain not complete.

I have set in the code for now to AccepAnyCertificate = true. I have also set HttpsCerticateAcceptancePolicy.AcceptAnyCertificate = true. Since I am connecting to the server which is availabe on internet I thought https certificates should be accepted. Worth mentioning that the server is Sign&Encrypt, Basic256Sha256 Seimence server.

Meanwhile I can connect with UaExpert to the server and verify the server but throws the exception when trying to connect with my C# client.

Could you help me on what I should do now?

I also found out some other people had the same exception in Online Forums but their application was different than mine, so I couldn't find the solution.

Best,
Ahmad