Click here to Skip to main content
15,887,812 members
Please Sign up or sign in to vote.
3.00/5 (1 vote)
Hi
I have a windows service which periodically connects remote web service method and passes the required parameters. This system was working perfect.

But for the live system, we needed to install and use client SSL certificate to call that remote web service method. Now, the windows servce returns the error below.

identity check failed for outgoing message. The expected DNS identity of the remote endpoint was 'thet-ws.ema.europa.eu' but the remote endpoint provided DNS claim 'TURSIGN'. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity 'TURSIGN' as the Identity property of EndpointAddress when creating channel proxy.

If I put TURSIGN as the identity like suggested, I receive the error;

Could not establish secure channel for SSL/TLS with authority 'thet-ws.ema.europa.eu:444'.

How can I resolve this problem?

Regards.
Posted
Comments
Mike Meinz 1-May-13 12:42pm    
I suggest that you have someone thoroughly check the DNS entries for thet-ws.ema.europa.eu. I used NSLOOKUP to get the IP Address (92.242.144.7) and then tried a Reverse DNS lookup using one of the public web pages that provide Reverse DNS Lookup service and got server can't find 7.144.242.92.in-addr.arpa error. Furthermore, if I use NSLOOKUP option set q=any, I get an error: Non-existent domain for thet-ws.ema.europa.eu
vucark 1-May-13 13:14pm    
Hi Mike.
The correct DNS address was thetis-ws.emsa.europa.eu:444 and the web service WSDL url
https://thetis-ws.emsa.europa.eu:444/thetis-data-exchange-integration-webservice/ClassInformationServices?wsdl
Mike Meinz 1-May-13 13:41pm    
NSLOOKUP results shows that portal.emsa.europa.eu is the actual server name for the server at IP Address 91.231.216.129. thetis-ws.emsa.europa.eu is an alias.

NSLOOKUP
> set q=any
> thetis-ws.emsa.europa.eu

Non-authoritative answer:
thetis-ws.emsa.europa.eu canonical name = portal.emsa.europa.eu

REVERSE DNS LOOKUP
Results
91.231.216.129 resolves to
"portal.emsa.europa.eu"

When accessing the web service, I got an error that said the certificate was not issued by a trusted certificate authority. Maybe there is a problem with the certificate. If you want to use SSL over the Internet, you should probably acquire a SSL certificate from one of the trusted authorities.
vucark 1-May-13 14:14pm    
Hi Mike,

This certificate is self signed. We got the signed certificate that they sent us. We have already installed that certificate. What do we need to do to make this client certificate trusted?
Mike Meinz 1-May-13 14:29pm    
If you are creating your own certificate, you must also create a certificate authority certificate and install that on every computer that will access your web site. Part of this CodeProject Tip may help you create the certificate authority certificate - How to be your own Certificate Authority and create your own certificate to sign code files

Almost everyone uses a trusted certificate authority because of the requirement that the certificate authority certificate must be on every PC that will access your web site.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900