We have an _intranet_ portal page that uses AD for authentication and authorization. When a user clicks a link to access a specific web application, the onclick event handler examines the user's AD group membership, and if the user is allowed to access the application, a record is inserted into a database table consisting of the sessionID, the user's name, the highest privileged group name, and some other stuff. When the user arrives at the destination web application, the application then checks the table for a record with the sessionID and determines what role the user is in based upon the group membership value. This may not be the best method of using AD for authentication and authorization, but it works well enough for now.
The problem is that one of the developers in our group has a fully implemented application that uses the roles and membership management system built into .NET 2.0, and we are tryi ...
Go to the complete details ...