OK, first I will say, NO. Second, here is what I would do. Create roles, because they are built into the .NET framework. 3rd, I would assign roles. amd then each role that is not "Admin", redirect to a certain page after login, and all Admins are sent to another page after login. Here is a visualization: Login.aspx | | Is user that logged in an Admin? (in the Admin role) | NO? |redirect to users.aspx |YES? redirect to admin.aspx
On Mon, Apr 20, 2009 at 12:11 AM, masterslave <[email protected]> wrote: > > Hey! > > I'm using ASP.NET 3.5 and need to create two login pages to control > access of users who are logged in to use e-commerce functionality as > well as admin users that need to go in and maintain the content. The > reason why I'd like to use two login pages in because they're > effectively accessing two different areas and I actually need to > validate login details from two different databases - main one for e- > commerce users and another one for admin users. Currently, > > <authentication mode="Forms"> > <forms name="OclCOMMERCE.AUTH" cookieless="AutoDetect" loginUrl="~/ > Login.aspx" protection="All" timeout="43200" path="/" > requireSSL="false" slidingExpiration="true" defaultUrl="~/ > default.aspx" enableCrossAppRedirects="false"/> > </authentication> > <anonymousIdentification enabled="true"/> > <authorization> > <allow users="*"/> > </authorization> > > Any advice much appreciated!! >
