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 ...Moving a DNN installationMoving a DNN installation
Previous
 
Next
New Post
10/9/2013 10:30 AM
 

I know there is a sticky on this exact subject, but the link in that post was killed by the move to dnnsoftware.com, the email address mentioned is of a company which I believe doesn't exists any more, so the sticky is useless and because the topic is locked, I can't reply there.

I'm using DNN 7.0.5, I want to have a local copy of my live server, for testing purposes. So I copied the database, copied the www-dir, and it works, except that I can't login. When I overwrite the passeword with a text and set the type to plain text, I can login.

Is there something which locks the encryption/hashing of the password field to a specific server?

 

In this topic I got the reply that "Most people manually copy their entire directory to the new server, back-up their database and restore it on the new database server." Is this something which worked in the past, but does not anymore? Or am I doing something wrong?

Ive read about a fix using some store procedure called something like dn_fixusers, but that seems to be very old (<2007)

 
New Post
10/9/2013 11:06 AM
 
What kind of security did you set on the folder where your site is located and what account did you assign dbowner rights in SQL? Did you use a Windows account for security or a SA account?
 
New Post
10/9/2013 11:08 AM
 

If you used a SA account you need to sync that:

 sp_change_users_login @Action='update_one', @UserNamePattern='Admin', @LoginName='Admin'

 
New Post
10/9/2013 12:04 PM
 
I have no specific security on the filesystem and the database user (username/password) is configured in the database and web.config.

How does the security on the folder or the database user name have anything to do with it?

DNN itself can access the database perfectly. it retrieves the page content and everything from the database. The user specified in the web.config works. (although the username is different from the username of the source site, but that's configured in both the database and the web.config) That's all security of the database.

It's just the user accounts (stored in the database) which don't work. It seems DNN can access the encrypted passwords, but the decryption goes wrong somehow, so passwords never match.

Does the database-owner have anything to do with the way the passwords of the dnn-users are stored? It could be that the database user name and file systems security settings are used as a pseudo random encryption key, but I would find that an unexpected approach to security on a system which can't even use hashed passwords.

 
New Post
10/9/2013 1:29 PM
 
There must be some sort of permissions set on the file system otherwise this will never work. Basically you can setup a DNN site with the iis apppool identity (best solution) or you should have a dedicated SA account that has also write permissions on the folder of your DNN instance.

You should use the first username with your DNN installation, the one you used to setup the site initially. Did you used the same web.config as with your installation?
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving a DNN installationMoving a DNN installation


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