Closed (cannot reproduce)
Project:
Protected Node
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Apr 2013 at 22:03 UTC
Updated:
12 May 2014 at 21:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
oadaeh commentedI don't know if this is related or not, but you might check out the patch I posted at #2044237: The module does not check if the password was changed to see if it fixes this.
Comment #2
izus commentedtested it but can't reproduce it.
i think it is solved with the current code base
Comment #3
britter commentedYou may want to check this out, just came across it in a build, if you sha1() the value of the password field per node on the way in (saving) you'll have to double sha1(sha1(the password)) on the way out as I believe the password field already encrypts it for you. So this will fix it on the way in (saving), you'll have to clear your existing passwords as they are double encrypted and will never match a single encrypted value.
Comment #4
dsoini commentedI have this problem if I set my nodes to use a global password. The password is not accepted. The patch does not fix the problem.