You can pass the identity between the two application domains call contexts, you'll need to implement ILogicalThreadAffinative interface for that. There's a simple example of this at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/ frlrfSystemRuntimeRemotingMessagingILogicalThreadAffinativeClassTopic.asp This doens't mean a secure connection, that could be achieved using https for example. Best Regards, RQ -----Original Message----- From: Alex Henderson [mailto:[EMAIL PROTECTED]] Sent: terça-feira, 11 de Junho de 2002 6:58 To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Secure remoting... Is there a standard way for securing a remoting connection so a remoted object can obtain the users identity/principal from the client/consumer of the remoted object - In java terms something along the lines of the "Common Secure Interoperability" features of the EJB 1.3+ spec. Cheers, - Alex You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
