locked
NetNamedPipeBinding from service to user process RRS feed

  • Question

  • I have a service that has to communicate with a user process. I am using

    new EndpointAddress(uri, EndpointIdentity.CreateSpnIdentity("host/localhost"));

    to create the endpoint for the host and the client. This only works when the user process is started with admin rights. Otherwise I will get a EndPointNotFoundException.
    The other direction ( service is hosting wcf and user process connects) it does not matter if the client has admin rights or not.
    So do I have to use HTTP binding instead of named pipes? The service should not be exposed to the network so I do not like to use http binding.

    • Edited by RZiller Thursday, April 8, 2010 1:50 PM html formatting was garbled
    Thursday, April 8, 2010 11:01 AM

Answers

  • Hi,

    You mean when user process hosting the wcf service, it works only under administrator account? If the user process is running under user account, you may try use UPN instead of SPN. By default, the SPN is used when service is running under LocalService, LocalSystem or NetworkService account. Please refer to this article.

    Service Identity and Authentication
    http://msdn.microsoft.com/en-us/library/ms733130.aspx

    Thanks,


    Mog Liang
    • Marked as answer by Mog Liang Thursday, April 15, 2010 2:01 AM
    Monday, April 12, 2010 2:34 AM