A
Avonelle Lovhaug
I have an ASP.NET application that is currently split into
3 separate VS.NET projects. One project is the
administration interface for creating web-based surveys
(uses windows authentiation). One project is the user
interface for providing surveys (forms authentication).
The last project is the user interface for checking survey
status (forms authentication). Each of these projects has
a separate group of authorized users. The projects
utilizing forms authentication verify users from a table
in a SQL Server database. The admin interface is only
available to a few internal users, which is why Windows
authentication was used - no reason to create a new table,
etc. just for internal users.
I would really like to rearchitect this application in
such a way that I can combine the app into one VS.NET
project. Right now, this application is deployed on a
single web server. The project for providing surveys is
installed in the root folder for IIS, and the other two
projects are installed in virtual directories off of the
root. I'd like to keep a similar structure in the new
architecture - placing the status and admin interfaces in
separate folders off the main application.
The problem I'm running into is that I can't mix Windows
and Forms authentication. I'm thinking that I may switch
to Forms authenticatio for the admin application, and just
set up a limited # of users in the web.config itself. But
is there a better way? And if I use forms authentication
for both the root project and the files in the two
folders, do those folders have to be set up as virtual
directories in order to have their own Login.aspx? Or will
everything go back to the same Login.aspx in the root
folder?
Has anyone else tried to do anything similar? Thanks.
--Avonelle
3 separate VS.NET projects. One project is the
administration interface for creating web-based surveys
(uses windows authentiation). One project is the user
interface for providing surveys (forms authentication).
The last project is the user interface for checking survey
status (forms authentication). Each of these projects has
a separate group of authorized users. The projects
utilizing forms authentication verify users from a table
in a SQL Server database. The admin interface is only
available to a few internal users, which is why Windows
authentication was used - no reason to create a new table,
etc. just for internal users.
I would really like to rearchitect this application in
such a way that I can combine the app into one VS.NET
project. Right now, this application is deployed on a
single web server. The project for providing surveys is
installed in the root folder for IIS, and the other two
projects are installed in virtual directories off of the
root. I'd like to keep a similar structure in the new
architecture - placing the status and admin interfaces in
separate folders off the main application.
The problem I'm running into is that I can't mix Windows
and Forms authentication. I'm thinking that I may switch
to Forms authenticatio for the admin application, and just
set up a limited # of users in the web.config itself. But
is there a better way? And if I use forms authentication
for both the root project and the files in the two
folders, do those folders have to be set up as virtual
directories in order to have their own Login.aspx? Or will
everything go back to the same Login.aspx in the root
folder?
Has anyone else tried to do anything similar? Thanks.
--Avonelle