Web Application Architecture Problem
Posted on 2008-02-08
BusinessLogicLayer (C# Class Library)
DataAccessLayer (C# Class Library)
I am developing an application where a user will log into a website and depending on the users login details they will be redirected to a particular section of the application. The application is very large and I would ideally like to split the sections into separate websites. Therefore the user will log into a website and then be redirected to the site that they have access right too. The application is far too large to just have separate sub directories in one website and use web.config files to handle authorisation and I would like to use the following standard architecture to achieve the goal of separation and easy build and maintenance of projects.
However I have a few questions regarding this solution:
1) Once logged into one website how do you pass authentication across to another site?
2) All sites share common UI elements such as style sheets, master pages etc. How can this be achieved?
3) Is this architecture the wrong solution for the project? If so does anybody have any recommendations?