This also doesn’t seem to fix it. Still I can login with Firefox and IE while logging in with Chrome is a no-go.
Hello, i have just upgraded from 2.4.8 to 3.1.1-2 and now i can’t login, noone can actually. I’ve:
- Cleaned
session
table - Cleaned
cache
folder - Ensured
session_cookie_name = OJSSID
and changed it, - Ensured
encryption = md5
- With
salt
commented or not -
session_check_ip
setting toOff
And now i still can’t login and can’t find where to look, anyideas @asmecher
Just to check it out, i generated another MD5 hash using user_name + user_password, changed at the database and the user was able to login again. My question is, why the new OJS can’t generate an md5 hash as OJS 2 was able to??
As i’ve many users in the database, i can’t regenerate all passwords. Any ideas @asmecher
Hi @lucasdiedrich,
OJS 3.x introduces a newer, more secure hashing method. When users with old password hashes log in, the hashes should be automatically converted over to the new format in the DB column.
Regards,
Alec Smecher
Public Knowledge Project Team