title: WCF, IPC Named Pipes, ASP.NET, and <identity impersonate="true" />
body: <p>We have a .NET 4.0 Windows Service that is hosting an endpoint over a Named Pipe (using IPC). This service is running under the context of User A.</p>
  
  <p>We have an ASP.NET-hosted client that is requesting the operation that is exposed by the aforementioned service. This client runs under the context of User B (via Anonymous Access ,via  <code>&lt;identity impersonate="true" /&gt;</code>).</p>
  
  <p>The problem:
  If we use <code>&lt;identity impersonate="true" /&gt;</code> in our web.config (this cannot be changed), we get "Failed to connect to an IPC Port: Access is denied." exceptions when the client tries to call the hosted operation. If <code>&lt;identity impersonate... /&gt;</code> does not exist (perhaps by virtue of not using ASP.NET, say a client Console Application), we have no issue.</p>
  
  <p>Does anyone out there know how to get this configuration working so we stop receiving Access Denied errors? It has something to do with authentication but we just can't work it out.</p>