Hello, 

I have two applications under the same domain:

domain.com/app1 and domain.com/app2

They were both created from the same app so they both have the same machinekey. And because of that they share the same auth cookie. So login on one portal You can then go to second one and user matches You will be logged in to second app also. And I want to prevent that. In normal asp.net I would just use two different names for auth cookie. But hereboth have the same  .dotnetnuke cookie name. Can I safetely change this name to something else or will that break dnn? 

Or do You know different way to prevent auth sharing? 

Thank You in advance

Lukasz

 

Yes, they are DNN based applications. After further investigation it looks like we changing cookie name won't help as You can change the name i.e. in dev tools.

So the question now is: How can I make sure that two applications under the same domain won't share auth cookie (if they have the same machinekey)? Setting path value to app name not always work because i.e. chrome is case sensitive here and if someone tyle app name i.e. App1 and we will have path="/app1" then it won't work and users won't be able to log in.

The problem is, that we already have two separate applications. In IIS they are as separate applications in separate app pools. The problem is, that they are in the same domain, so they look like: domain.com/App1 and domain.com/App2. So they share the same cookie. And because they both have the same machinekey, shared cookie can be use to access both sites.

So to make it clear, changin auth cookie name from .DOTNETNUKE to i.e. .DOTNETNUKE2 will break DNN?