Hello.
I have a remote object hosted by Windows Service (not IIS). I want it to be
available over the web. How can i secure it by login/password? Or i have to
pass login and password as the parameters every time i call my remote
methods?
Richard Bell - 29 Jun 2004 08:27 GMT
One of the most compelling reasons for using IIS to host your remote objects
is that you get security out of the box. You might find life a lot easier if
you reconfigure your remote objects to be hosted by IIS, or alternatively,
if that is impractical for some reason, code a new object which delegates
calls to your service and remote that from IIS.
> Hello.
> I have a remote object hosted by Windows Service (not IIS). I want it to be
> available over the web. How can i secure it by login/password? Or i have to
> pass login and password as the parameters every time i call my remote
> methods?
Allen Anderson - 29 Jun 2004 15:08 GMT
Check this article from microsoft out.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/S
ecNetch11.asp
Personally when I need security and I'm using stateful remoting
objects, I use encrypted channels and do my authorization manually at
the start.
Allen Anderson
http://www.glacialcomponents.com
mailto: allen@put my website base here.com
>Hello.
>I have a remote object hosted by Windows Service (not IIS). I want it to be
>available over the web. How can i secure it by login/password? Or i have to
>pass login and password as the parameters every time i call my remote
>methods?