HashPasswords process update DatePasswordChanged
36 views
Skip to first unread message
Nicolas Micoud
Apr 26, 2018, 10:22:14 AM4/26/18
to iDempiere
Hi,
I've executed the HashPasswords process on my test instance.
Just notice it has updated the DatePasswordChanged.
I don't think that is correct as the password didn't change (just the way it is stored).
Right after the user has been saved (with hashed password), we should put back the "original" date (using direct SQL ?)
WDYT ?
Nicolas
I've executed the HashPasswords process on my test instance.
Just notice it has updated the DatePasswordChanged.
I don't think that is correct as the password didn't change (just the way it is stored).
Right after the user has been saved (with hashed password), we should put back the "original" date (using direct SQL ?)
WDYT ?
Nicolas
Carlos Antonio Ruiz Gomez
Apr 26, 2018, 11:07:06 AM4/26/18
to idem...@googlegroups.com
Maybe an easier way could be to move the line 936 in MUser to line 929
(in the else part of not being hashed)
setDatePasswordChanged(new Timestamp(new Date().getTime()));
I haven't tested, but I think it could work.
Regards,
Carlos Ruiz
> --
(in the else part of not being hashed)
setDatePasswordChanged(new Timestamp(new Date().getTime()));
I haven't tested, but I think it could work.
Regards,
Carlos Ruiz
Carlos Antonio Ruiz Gomez
Apr 26, 2018, 11:09:58 AM4/26/18
to idem...@googlegroups.com
Sorry, I mean line 947 to 939 in current version 5.1 (I was looking a
different version)
different version)
Nicolas Micoud
Apr 27, 2018, 3:11:15 AM4/27/18
to iDempiere
Reply all
Reply to author
Forward
0 new messages