We are currently designing a solution that will run as a .Net Web application behind a WebSeal reverse proxy.
We have an application which relies heavily on Adobe Spry. For authentication purposes a Single Sign On Solution is used. (Its a WebSeal, but I don\'t think that matters to much)
I\'ve run up across a problem with ASP.NET AJAX (hooked up to WebServices directly) and accessing our site through a WebSeal junction.
Consider the following setup: A webapplication deployed on a Websphere Application Server (6.1 if it matters)