G
Guest
I have what I'd *like* to be a single web application (meaning, shares the
same Session object for a given user, etc.). But I'd like to configure it for
FormsAuthentication so that if the user goes into most of the directories
before he's authenticated, he'll go to one Login.aspx whereas if he goes for
the first time to, say, "/Admin/*", he gets a different Login.aspx page. Both
pages will end up authenticating the user the same way, but the UI, etc., of
the Login pages will be dramatically different. Is there any way to configure
this in web.config files? Or do I have to do it programatically in the
Login.aspx page?
Alex
same Session object for a given user, etc.). But I'd like to configure it for
FormsAuthentication so that if the user goes into most of the directories
before he's authenticated, he'll go to one Login.aspx whereas if he goes for
the first time to, say, "/Admin/*", he gets a different Login.aspx page. Both
pages will end up authenticating the user the same way, but the UI, etc., of
the Login pages will be dramatically different. Is there any way to configure
this in web.config files? Or do I have to do it programatically in the
Login.aspx page?
Alex