WCF security problems with named pipes

Question

I have a slightly complicated setup that, of course, works fine in XP, but chokes on Windows 7. It may seem like madness, but it made sense at the time!

I have a WPF app

Answer 1

The applications (WPF/Console) are creating locally scoped named pipes (this happens by default when they are unable to create globally scoped pipes). My guess is that they can communicate with each other because they can see each others named pipes because they are running under the same account.

The windows service has higher privileges and can therefore create a globally scoped named pipe for the client applications to see.

You can check out a discussion on Christian Weyer's Blog.