Home/ Questions/Q 3981916
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T05:28:03+00:00

This should be a snap for anyone who’s done it before… I’m trying to

  • 0

This should be a snap for anyone who’s done it before…

I’m trying to set up a self-hosted WCF service using NetTcpBinding. I got a trial SSL certificate from Thawte and successfully installed that in my IIS store, and I think I’ve got it correctly set up in the service – at least it doesn’t exception out on me!

Now, I’m trying to connect the client (this is still all on my dev machine), and it’s giving me an error, “Message = “The X.509 certificate CN=ssl.mydomain.com, OU=For Test Purposes Only. No assurances., OU=IT, O=My Company, L=My Town, S=None, C=IL chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.”

Ooookeeeey… now what?

Client code (I want to do this in code, not app.config):

var baseAddress = "localhost";
var factory = new DuplexChannelFactory<IMyWCFService>(new InstanceContext(SiteServer.Instance));
factory.Endpoint.Address = new EndpointAddress("net.tcp://{0}:8000/".Fmt(baseAddress));
var binding = new NetTcpBinding(SecurityMode.Message);
binding.Security.Message.ClientCredentialType = MessageCredentialType.UserName;
factory.Endpoint.Binding = binding;
var u = factory.Credentials.UserName;
u.UserName = userName;
u.Password = password;
return factory.CreateChannel()

Added Bounty
I’ve just got myself a new trial certificate from Thawte, installed it with the “issued to” set to mydomain.com, and I’m still getting the error above. I’m a newbie to web security, so I’ll need detailed instructions how to get a client to connect to my website and accepting the security certificate. (BTW, what does “No assurances” mean?)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem seems to be that the server certificate you have installed on your server is not trusted by the client.

    For it to be trusted the root CA certificate of the server certificate needs to be in the “Trusted Root Certification Authorities” store of the user running the client. If you get a “production” level server certificate from Thawte or some other similar CA it will already be trusted by most machines in the world.

    However, judging by the error message (where the subject distinguished name of the certificate contains “OU=For Test Purposes Only. No assurances.”) your certificate is a test certificate and you therefore need to add the CA certificate to your “Trusted Root Certification Authorities” store manually. The root certificate can usually be downloaded from the CA’s (Thawte in your case) website.

    • 0