Hi,

I'm trying to build a prototype for an umbraco solution that requires me to have around 5-6 variations of the same application running in a single instance. As I'm forced to work against a legacy database for memberships and roles, I've extended the UmbracoMembership and the UmbracoRole providers, overriding them with some custom logic.

It is a requirement, that if you are logged into one of these 5-6 variations, you are not to be logged into any other. The way i have it setup, my variations are simply seperated by part of the URL. For instance, one might login into variation one at http://mydomain.com/variation1/frontpage.aspx and another at http://mydomain.com/variation2/frontpage.aspx.

Currently, if you log in at http://mydomain.com/variation1/frontpage.aspx and change variation1 to variation2, you will of course still be logged in, now - conceptually - in another application which is not the intent.

As this is only my second umbraco solution, and my first attempt at running multiple sites in one, i have no idea if I am going by this in a sensible way. I am guessing that this problem is not so much about umbraco, as it is more general.

Any help to handle this scenario would be appreciated.

Cheers