You can use integrated Windows authentication if your remoted component is hosted in IIS and it works well, though it can be rather slow so avoid making lots of fine-grained calls to your remoted component. I was under the impression that it will work through a firewall (with port 80 open, obviously) but that there are problems using it with some web proxy servers but I could be mistaken - anyone know for sure ?
The SSPI channel in framework 2.0 is based on a pair of articles published on MSDN about a year and a half ago. Search for "SSPI remoting" on MSDN and you'll find them and the related source for a version which works with framework 1.1. It works pretty well and is quite a lot faster than IIS integrated authentication. Glenn -----Original Message----- From: Ian Griffiths [mailto:[EMAIL PROTECTED] Sent: 29 August 2005 22:21 To: [email protected] Subject: Re: [ADVANCED-DOTNET] Reasons to use HTTP remoting > 2) Although not required, it is helpful to use HTTP remoting to > utilized the security functions of IIS, correct? I gather it's possible to do integrated authentication too, although I've never done it myself. If you can wait for Whidbey, it has an SSPI channel that provides integrated authentication and encryption without the need to rely on IIS. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
