Replacing ISAPI web authentication filter with .NET solution?

[Gregory Gadow]

Currently, my company's website uses a custom ISAPI filter to map a web
user to a network user, and give the user access to our website. This
has worked great for several years. We now want to add .NET
functionality to our website, and I am looking for a .NET solution to
replace the ISAPI authentication. We have Visual Studio 2005, SQL Server
2005 and IIS 6.

With the current setup, user id, password and the network user id are
stored in a separate table on SQL Server. I would like to retain that
structure, as we already have several tools for maintaining the data. I
have considered a custom implementation of ProfileProvider, but the
documentation is piss-poor and all reference SQLExpress, which is not on
our web server.

What I need is: What is the recommended .NET equivalent to a web
authentication ISAPI filter? Can someone provide a good example of such
a solution (VB preferred or C#) that does NOT use the default Profile
table structure?

Thanks for any help.

 

[Jesse Houwing]

Currently, my company's website uses a custom ISAPI filter to map a web
user to a network user, and give the user access to our website. This
has worked great for several years. We now want to add .NET
functionality to our website, and I am looking for a .NET solution to
replace the ISAPI authentication. We have Visual Studio 2005, SQL Server
2005 and IIS 6.

With the current setup, user id, password and the network user id are
stored in a separate table on SQL Server. I would like to retain that
structure, as we already have several tools for maintaining the data. I
have considered a custom implementation of ProfileProvider, but the
documentation is piss-poor and all reference SQLExpress, which is not on
our web server.

What I need is: What is the recommended .NET equivalent to a web
authentication ISAPI filter? Can someone provide a good example of such
a solution (VB preferred or C#) that does NOT use the default Profile
table structure?

Microsoft has released the sources for the provider model of ASP.Net 2.0
to the public. (see
http://weblogs.asp.net/scottgu/archive/2005/08/01/421275.aspx)

This should give you a template to work on.

Jesse Houwing