I just upgraded one instance of DNN from 3.1 to 3.2.2 and the passwords from the host and admin accounts were invalidated somehow. This happened in my development environment - we have 4 environments: local dev, shared dev, test, and production. Everything worked beautifully in my local dev; however, when I deployed to the shared dev server, I couldn't login.

I haven't upgraded my test server, but that's my next step. I was hoping to find out if this was a random mishap or if there's something I really have to be aware of in the upgrade. Obviously, I can't risk all my users' passwords being reset.

My guess is that there was a change in the algorithm that validates the passwords using the password salt, but I'm not sure what that may have been. Any help is appreciated.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

I did that once.  I somehow introduced an extra carrage return in the MachineKeys in web.config

---

Paul Davis

Thanks, guys. That was the problem. I figured it out by just deploying to the test server and paying more attention to the web.config. At least I saved the old config file.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com