Authenticating user through more than one login page for mobile part of webpage, C#

[Sleepwalker]

Hi,

I'm currently working on creating a stripped down part of a company web page, that will be accessed from cellphone. The problem I have is that the Windows Forms authentication makes it difficult for me to create more than one login page. In my web.config file I have it set so that unauthenticated users will be directed to the default.aspx page which handles logging in. As part of the default.aspx Page_Load I transfer users to a mobile/login.aspx page in case the browser.IsMobile is true.
However, before my login code in mobile/login can be executed, the forms authentication detects that I'm not logged in, and redirects me back to default.aspx, which in turn redirects me to mobile/login.

I have thought of several possible ways to solve this, but I haven't found any good information on it.

One way would be if it is possible to specify multiple login pages in the web.config file that would prevent default.aspx to load if I'm accessing the mobile login page. Can this be done?

Another thought was to make the default.aspx into both desktop and mobile login, by mixing asp: and mobile: content. Does anyone know if this is possible? Is it possible to have both a mobile:Form and an asp:content, the compiler seemed to dislike the idea. This would also require that I created a filter or devicefilter that detected all mobile devices and checked against it at the start of the default HTML code. Is there a clean way to do this or would I have to create a separate check with the compare argument against every brand and type of cellphone?

Best,

Erik

[kenobewan]

Why wouldn't you have browser check in in your default page_load and redirect if browser.IsMobile true?

[Sleepwalker]

Why wouldn't you have browser check in in your default page_load and redirect if browser.IsMobile true?

The redirection works alright, but it still doesn't allow me to sign in through the mobile login when I'm using a cellphone emulator. The problem is that once I've attempted to login, I'm still directed back to the orignal login page withough authentication. I've fixed better redirection by using <location > tags in my web.config where I allow all users to access the mobile login. However, the problem still persists. At the end of my Authentication method, I add an auth cookie and a user preference cookie to the Response Cookie list, for a total of three cookies. I then redirect the user to the page they want to see, in this case mobile/home.aspx. However, after the Redirect, the two cookies are somehow deleted and since no auth cookie exist the browser defaults back to default.aspx once again. Does this behavior sound familiar? I'm using the latest OpenWave simulator and I've checked so that it accepts cookies, so that shouldn't be the problem.

Thanks,

Erik

[Sleepwalker]

I've tracked the problem a little further, and it seems that when the Application_AuthenticateRequest is called in Global.asax.cs, the cookies are all gone, and there is no HttpContext.Current.User object, which there should be. Does this mean anything to anyone? Could it be some mobile specific thing?