How to secure a WCF service using NetNamedPipesBinding so that it can only be called by the current
Posted
by Samuel Jack
on Stack Overflow
See other posts from Stack Overflow
or by Samuel Jack
Published on 2010-03-19T12:57:59Z
Indexed on
2010/03/19
13:01 UTC
Read the original article
Hit count: 583
I'm using a WCF service with the NetNamedPipesBinding to communicate between two AppDomains in my process.
How do I secure the service so that it is not accessible to other users on the same machine?
I have already taken the precaution of using a GUID in the Endpoint Address, so there's a little security through obscurity, but I'm looking for a way of locking the service down using ACL or something similar.
© Stack Overflow or respective owner