Not by default; identity information is not propogated across the remoting channel. You could either build this transparently into the channel (the easiest way is probably building a pair of channel sinks) or you could do it a bit more explicitly using the CallContext (easier to implement, but much less transparent).
I think I saw an example of a channel sink like I mention above posted somewhere, although I don't remember where. You might check the archives. Greg Reinacker Reinacker & Associates, Inc. http://www.rassoc.com http://www.rassoc.com/gregr/weblog/ -----Original Message----- From: The DOTNET list will be retired 7/1/02 [mailto:[EMAIL PROTECTED]] On Behalf Of Jose M. Nobre Sent: Friday, June 07, 2002 10:39 AM To: [EMAIL PROTECTED] Subject: User auth. using Remoting/TCP Hi... Is there an implicit way for a given service (exposed through remoting/TCP) to know wich user is calling it?? thanks in advance jmn You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
