Nathaniel Engelsen » target principal name is incorrect http://nathanielengelsen.com Thu, 03 Dec 2009 13:03:01 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Windows Communication Framework (WCF) — Eliminating Principals on Endpoints http://nathanielengelsen.com/2009/09/windows-communication-framework-wcf-eliminating-principals-on-endpoints/ http://nathanielengelsen.com/2009/09/windows-communication-framework-wcf-eliminating-principals-on-endpoints/#comments Tue, 01 Sep 2009 16:08:17 +0000 nathaniel engelsen http://nathanielengelsen.com/?p=139 I don’t need to securitize my WCF services with windows principals at this point — at this point I tend to want various and sundry types to be able to access them. To affect this, I need to use a blank identity when I go to consume an endpoint.

From stackoverflow.com I saw that you can pass in an blank SpnEndpointIdentity when instantiating your communication layer:

    using con As new OfferingTap.OfferingTapClient( _
        new ServiceModel.InstanceContext(callback), "NetTcpBinding_IOfferingTap", _
        new ServiceModel.EndpointAddress(new Uri("net.tcp://qa1offerings:8190/"), _
        new ServiceModel.SpnEndpointIdentity("")))

In my config file, however, I just zap it out:

<endpoint address="net.tcp://localhost:8700/PCFComms/service"
    binding="netTcpBinding" contract="PCFCommsGateway.PCFCommsService"
    name="PCFComms">
    <identity />
</endpoint>
Share:
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • DotNetKicks
  • HackerNews
  • LinkedIn
  • Reddit
  • Slashdot
]]> http://nathanielengelsen.com/2009/09/windows-communication-framework-wcf-eliminating-principals-on-endpoints/feed/ 0