Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"Wrong Username and password combination" after upgrade to 3.x #12536

Closed
jacobweber opened this issue Feb 4, 2018 · 3 comments
Closed

"Wrong Username and password combination" after upgrade to 3.x #12536

jacobweber opened this issue Feb 4, 2018 · 3 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@jacobweber
Copy link

I upgraded Piwik from 2.17.1 to 3.2.1. It's using PHP 5.6.29 and MySQL 5.7.18.

The core:update step initially failed (lost the connection to the DB), so I followed the instructions. I manually re-ran the remaining queries, updated the "version_core" option to 3.2.1, and re-ran core:update successfully.

Afterwards I was unable to log in with any existing users. I could reset their passwords, and then they could successfully log in. But I'm afraid I missed something, since existing users should have worked.

As part of the manual queries, I ran:

ALTER TABLE `piwik_user` CHANGE `password` `password` VARCHAR(255) NOT NULL;

So the column length was changed. But there was nothing that changed the actual values. All of the existing users had 32-character passwords. Once I reset my password, its length was changed to 60 characters.
@sgiehl
Copy link
Member

sgiehl commented Feb 4, 2018

The password hashing algorithm has been changed in #10740
Guess the update script for updating the passwords didn't run due to the failure: https://github.com/mneudert/piwik/blob/3.x-dev/core/Updates/3.0.0-b4.php#L76-L95

@sgiehl sgiehl closed this as completed Feb 4, 2018
@sgiehl sgiehl added the answered For when a question was asked and we referred to forum or answered it. label Feb 4, 2018
@jacobweber
Copy link
Author

Shouldn’t the update script print out the SQL for re-hashing the passwords, when it prints out all the statements in the “dry-run” section? The instructions for dealing with a failure tell you to finish running all the SQL statements, so it should probably include those.

@sgiehl
Copy link
Member

sgiehl commented Feb 4, 2018

No. Not in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jacobweber @sgiehl