Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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 StartedInstalling DNN ...Installing DNN ...dual install security problemdual install security problem
Previous
 
Next
New Post
10/28/2008 5:11 AM
 

<p>I have installed DNN and it is running fine on my domain. I then wanted to have a second installation running on a separate port to act as a test environment.</p> <p>e.g. <a href="http://www.mydomain.com">www.mydomain.com</a> and <a href="http://www.mydomain.com:8000">www.mydomain.com:8000</a></p> <p>To do this I copied the original install directory, and created a second database from restoring the original too.</p> <p>Both installs run, but I have a security issue. If I log into either site, the login allows me access to both sites. This even happens if i change the password on the user account. I want to have a test environment which I can provide access to users to review content etc, and allow testing of installs and skins. But it must behave as a self-contained site.</p> <p>Can anyone suggest how to solve this problem?</p>

 
New Post
10/28/2008 5:51 AM
 

why not create a new subdomain?


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
10/28/2008 9:55 AM
 

How would IIS need to be configured?

It just seems strange, that 2 installs should interact in this way.

 
New Post
10/28/2008 3:16 PM
 

I believe the issue is that the cookie gets sent to both domain names as they are the same. Your browser assumes you're accessing the same site (even though through a different port) and it will send the cookie that was set for authentication to both sites. Since they are identical copies, the cookie matches the internal system's authentication mechanism and you're in. This is not a bug but a feature you're experiencing ;-)

What Erik suggested is indeed the most logical. I do this all the time as well. It is common to have a 'www.mydomain.com' and a 'staging.mydomain.com'. Your browser sees these as different sites and will not send cookies from one to the other. Set it up in IIS as different sites with different 'host headers'. Check IIS documentation for that.

Peter


Peter Donker
Bring2mind http://www.bring2mind.net
Home of the Document Exchange,
the professional document management solution for DNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...dual install security problemdual install security problem


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