Our organization is planning on using Webseal as a proxy sitting in front of our .net web sites. We are currently using .net forms authentication and a custom membership provider against a custom sql server user table.
Under this new model, all authentication would be done by the webseal layer. From what I understand, once authenticated, webseal would just add a token in the header indicating that the user is authenticated along with the userid.
I'd like our apps to work with no changes so I want to build something to shield them from the details of webseal by building some layer that converts the webseal token to a regular .net token.
I'm not sure where this should be done...in some kind of custom authentication provider, or a new membership provider or ? I don't want any of our apps to have to make any changes other than to maybe use this new code if it is an http module or other provider.
Has anyone done this type of thing? What would be a good strategy for this. I've heard of Windows Identity Framework but not sure if it is the right solution for this.
Any advice or direction would be helpful.