Update 2013 to 2019 – cant login

[Martin-S]

was running ver. 2013.1.beta.7
after a server migration using PHP 7.x, some functionality are not working (Emails).
I’ved followed the instruction to uptade to master_2019.2
Copied the old config.php to config folder.
After files where uploaded, i cannot login.
Err: Invalid User ID and/or Password!
Looked in DB: username is there.

[RRowley]

Look in your tmp/log/php.log file to see if there is more of an explanation. If you need me to look at it, copy the log file to a zip file and attach that zip file to a response to this message.

Also note what OS you are on and what webserver software you are using.

[paulr]

I discovered that I had this issue too, so I changed Line 19 in the config file to:

authentication.enabled = true

which allowed me to log into the demo account.

From there I went to People > Users and then I changed the password for my user.

Note the requirements for new passwords:

Passwords must…

Begin with an alpha character
Be at least 8-characters long
Contain no blanks
Contain at least one upper case character
Contain at least one lower case character
Contain at least one numeric character
Contain at least one special character

My old password was not formatted this way, so maybe this had something to do with it.

Once I saved this change, I then modified Line 19 in my config file referenced above to true.

From there, I was then able to log in to SimpleInvoices using my username and the new password.

Note that there is no ‘Log Out’ link when logged in with no authentication. So what I did was open SimpleInvoices in a new *private* browser window to force me to login without use of the prior cookie.

Hope this helps!

Paul

[RRowley]

If the authentication option in the config file is set to false, the user is not relevant. Since there is no log in, there is no logout. When authentication is enabled, the user is pertinent. Typically, if a user already exists, the same password should work. The rules for what a new password must conform to does not apply to existing passwords. What I believe the issue would be, is that there has been a change in the algorithm used to hash the password has changed. The authentication logic however takes this into account. If the password fails authentication using the new algorithm, it attempts authentication using the old algorithm. If that succeeds, it updates the password on file using the new hash for all future login attempts. In practice, I found that I would have to login a second time to have the newly encrypted password work. If this process didn’t work for you, I’m at a loss as to why. I’m glad however that you were able to get it working.

[Author]

Posts