WCF and Wildcard Certificates with NetTcp binding

Asked May 05 '16 at 10:03

Active May 06 '16 at 08:17

Viewed 581 times

I have a self hosted WCF service using a NetTcp binding and TransportWithMessageCredential security with a wildcard cert (*.company.com) as the service certificate.

The client address of the server is (ServerName.company.com) I get the following error when a service call is made:

Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was 'ServerName.company.com' but the remote endpoint provided DNS claim '*.company.com'. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity '*.company.com' as the Identity property of EndpointAddress when creating channel proxy.

Is this actually possible? Any help is appreciated.

edited May 06 '16 at 08:17

asked May 05 '16 at 10:03

Sjblack

Can you add your configuration ? – Rom Eh May 20 '16 at 09:41
There is a similar question with answers over here: [WCF Identity Check](http://stackoverflow.com/a/1630238/2661476) – tjhazel Jun 30 '16 at 14:55
This could also help: https://stackoverflow.com/questions/24385815/wcf-over-https-using-a-wildcard-ssl-certificate – OlafW Jan 02 '18 at 13:05
Please post the code you are making this call with, – smehaffie Mar 30 '18 at 03:19

WCF and Wildcard Certificates with NetTcp binding

0 Answers0