Two of the most powerful features of the .NET Framework are Remoting and Security. Remoting is a mechanism for communicating between distributed objects, and. Security has been worked into almost every aspect of the .NET Framework. Unfortunately, there is currently only one default way to combine these two to provide secure remote method calls.

Fortunately, one of the great features of Remoting in .NET is that it is extensible. In this article, author Matthew Milner will show how to create a remoting channel sink that can be transparently plugged into a configured remoting application to transport the current security principal from the client to the server. Additionally, we will see that this information can then be used to constrain the actions available to the user within the remote object using security demands.