PublickKeyTokenProvider: Fix password update routine with password hash
fixes #33757
@marcelklehr Do you think this PR could be tested on production server? We have like 600GiB of WAL every 2 days (for a DB that weights less than 200GiB), it puts a real burden on our backup server.
Let's wait till this is merged @ldidry
Ok, thx. :slightly_smiling_face:
follow up from https://github.com/nextcloud/server/pull/33485
/rebase
Cypress failure looks related (500 error on the login)
Maybe naive, but couldn't we compare the value of decrypted password ?
We cannot decrypt all tokens of a user to update them as we only got the user password when the update is called, not the actual cipher to decrypt the tokens (e.g. the app passwords).
For some reason the migration isn't executed before the cypress tests run. Help is appreciated.
For some reason the migration isn't executed before the cypress tests run. Help is appreciated.
I had the same issue in another PR. Let me see if I can come up with a generic solution
https://github.com/nextcloud/server/pull/35889 should fix the issue.
Should be good to merge now
Pushed another commit to bump the version and trigger the db upgrade on existing setups.
Failure unrelated
This basically breaks Talk integration tests.
On each login the password column as well as password_hash of oc_authtokens is changed, for all entries, although the user password never changes (admin:admin).
/backport to stable25