Hi, I dont know if I should post this here or somewhere else but... here we go....

I know that there's user table in DNN Database contains the user ID, username, First, Last, is super user, affiliateID and Email. But where is the pwd and other details (address, phone, etc) stored?

Thanks if you can help me with this....

And is there anything we can do here to 'reset' the passwords via Enterprise Manager or similar Roger?  The reason I ask is last week I got 'logged out' of a new DNN 3.2.2 installation.  I'd only set the host and admin accounts up with new passwords, but I got logged out, and no matter what I did I couldn't get back in.   In the end I removed the DNN install, and the DB and reinstalled DNN.  This time I set up another SuperUser account and another Admin account.  Then today I have again been shut out of DNN and none of my passwords work.  Not for the Host/Admin or the two new accounts.  And to cap it, when you request the password to be sent through, the new SuperUser one comes through with ***** (like a Host password request) and the other admin account comes through blank.  Ie. there is NOTHING next to Password: in the password retrieval email.

It seems as I look for a solution to this that there are other user out there who are experiencing similar problems.  Is it not possible for the DNN development team (who are doing a great job btw) to configure the passwords in the standard User table, so if something like this happens we can at least access the DB via EM and manually change/add/edit them.  It would be nice to have the 'choice' to have the passwords encoded (understand the added security benefits here, but really, if someone's got access to your DB they can do damage without seeing your passwords) or not? 

Just a thought. Meanwhile, I'll keep looking for a solution so I don't have to rebuild my DNN app for the 3rd time and now have to re-enter all my site content from the last week.

If anyone has a solution to this password issue, that's a simple step by step, I'll 'love you forever' if you could post it

Thanks,

Reuben.

Good thread!

I too have been wrestling with this "encrypted password" issue, and related problems caused by the difficulty accessing an existing (populated) SQL database from a brand new install of DNN portal.

Would I be correct to assume that the encryption key/salt buried in the web.config can be saved and then inserted into the web.config of a subsequent portal? Would that solve the problem of accessing an existing database from a new, or additional, portal?