[SOLVED] single membership providers within ASP.Net MVC 3 application sharing between 2 webapplications

single membership providers within ASP.Net MVC 3 application sharing between 2 webapplications

We have 2 different mvc web applications running on single membership provider. I have put these 2 applications on the webserver and has the virtual path: http://aa.svr1/app1 http://aa.svr1/app2

If user opens the app1 and app2 in seperate browsers it logs out the other aplication. When user uses one application at a time, no issuess, concurrently used, its giving log off in one of the application.

I have put the machinekey in web.config file for app1 application and was working fine. I have made new tfs release onto live server, now again back to the same situation that when app1, app2 browsed simultaneoulsy, logging off one of the application.

What could be causing this blocking sessions/behaving unexpectedly like this ?

Solution

You could try explicitly specifying the path parameter of the authentication cookie:

<forms loginUrl="~/Account/LogOn" timeout="2880" path="app1" />

or simply use 2 different cookie names:

<forms name="app1auth" loginUrl="~/Account/LogOn" timeout="2880" />