-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix(oauth2): adjust db schemas when migrating from owncloud #50193
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
Conversation
ChristophWurst
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good so far
|
/backport! to stable29 |
91c93e1 to
0fc1f08
Compare
|
/backport to stable30 |
|
/backport to stable31 |
Signed-off-by: Richard Steinmetz <[email protected]>
0fc1f08 to
754a047
Compare
|
/backport to stable29 Let's recreate the backport as it was incomplete. |
| \OC::$server->getConfig() | ||
| ), | ||
| new MigrateOauthTables(\OC::$server->get(Connection::class)), | ||
| \OC::$server->get(MigrateOauthTables::class), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| \OC::$server->get(MigrateOauthTables::class), | |
| \OCP\Server::get(MigrateOauthTables::class), |
Next time 😉
oc_oauth2_access_tokensis not adjusted properly and its data is not migrated correctly when migrating from ownCloud #50186Summary
See also #49075
This PR fixes two issues:
It does not aim to migrate legacy access tokens from ownCloud as this incurs a lot of work and tokens are only valid for an hour. So, it does not make sense as the migration window set by admins is probably longer than their lifetime anyway.
What I tested
mysqldump owncloud oc_oauth2_access_tokens oc_oauth2_refresh_tokens oc_oauth2_clientsoc_oauth2_access_tokens,oc_oauth2_refresh_tokensandoc_oauth2_clients).occ migrations:migrate oauth2 && occ maintenance:repairTODO
Checklist