We have used the server “Check Passwords” for some time, and when we set the person document to “Do Not Check Password,” it didn’t check passwords, nor did it hash the password presented. We set a person to “Do not check,” removed the current password hash, and saved the doc. We do this when they are reinstalling or otherwise need others to get into the account.
Since upgrading to 601cf1, seems that the next login, the person’s password is again hashed, and they or the support team are again locked out. Shouldn’t the person doc tell the server to not bother with this person? That’s the way it worked in previous (5.09) installations.
Has anyone else noticed this with 601cf1?