Products

Solutions

Resources

Partners

Community

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Auth cookieAuth cookie
Previous
 
Next
New Post
2/6/2018 5:16 AM
 
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

 

 
New Post
2/6/2018 11:31 PM
 
Jan,
Is this question related to DNN Platform product?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/7/2018 10:56 AM
 
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.
 
New Post
2/8/2018 12:15 AM
 
cookie name is fixed. DNN is an application using a dedicated auth cookie, you cannot use auth cookies for modules.
if you want to install two DNN instances within a single IIS website, you need to create two applications and map one virtually into the other or both into a shared Website folder.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/8/2018 2:44 PM
 
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?
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Auth cookieAuth cookie


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out