asp.net mvc membership - caches login info and shows on different applications

Question

I've asked similar question here because I thought the problem was in my custom membership provider.

Then I tried this:

I created two NEW asp.net MVC applications. In first one, I registered as new user using default membership provider. I closed this application, opened second one and ran it. In this application I was also logged in as user I created in first application. Logging in as user from other application doesn't work, but caching is remembered on this site. Why is it so? Is it a bug?

Answer 1

I think this can be expected behaviour:

If you open localhost/app1 and localhost/app2 you are on the same domain. So its valid that the same cookie is sent. I am not shure if localhost:5050 localhost:5060 are considered as the same domain. But I guess thats the case.

If the same cookie is sent the Memebershipsystem will evaluate this as the same user. Thats expected behaviour.

If you want to have these 2 webs use different pools of users you have to create a new application in the Mebershipsystem and configure it in web.config.

This will not affect the behaviour of a production system, because the 2 web will be on a different domain. each domain is only allowed to access its own cookies.