I came up with a scheme for the following scenario:
A collection of forms sites that were to be migrated to Windows authentication, more or less one at a time, with single sign-on capability while the migration was taking place and eventually all user accounts were to be stored in Active Directory. Some users, both internal and external, were in Active Directory, all others were in a SQL Server membership store. Two entry points: user type A go here to log in, user type B go there to log in, was completely out of the question per business requirements. Users presented with more than one login prompt was also out of the question. Let it suffice to say that bringing all of the web applications to use Windows at once was unreasonable and most of them relied heavily on custom authorization and a forms-based security (some classic ASP mixed in there as well). Moving ahead, however, we realized that using Windows' native security across the board was to our advantage. Our one ad ...
Go to the complete details ...