I have been designing several add-on style pieces for sites that I have been creating (asp.net 2.0, vb)... for example, a database driven javascript news scroller, a web-based e-mail newsletter app, a paypal-based database-driven shopping cart app, etc. For the most part, these are based in sql server, though one or two are access-based (I am eventually developing both versions for all applications)

I have so far developed each one of thse add-ons indiviudally, and have encountered a problem when trying to implement more than one of them on the same site. I am using forms authentication to verify user credentials against the database... which forwards unauthenticated requests to *one* login.aspx page. This is done in the root-level web.config file, and moving the authentication tag out of the root-level config file is not allowed.

I hope I am correct in assuming that there is a way to authenticate against different sets of user names and passwords for different sections of the site.

I had considered combining all login information into one table and assigning different roles for the different sections of the site, but somehow this does not seem like the best solution.

Any help is appreciated, hopefully in my informal .net training I have missed something that will be of use :)