Preserve OAuth connection IDs during vault migration - #484
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The vault migration assigned new IDs to OAuth grants. Inbox Manager and X Me retain the old connection IDs, so their accounts lose access after an upgrade. Preserve each OAuth connection ID when inserting its vault row.
Verified the full upgrade on a production database copy: all five OAuth IDs and refresh tokens survive, both app account references resolve, and all vault entries decrypt. Ruff lint and diff checks pass. The format check reports existing formatting outside this change. No tests added or run.
Fixes DRU-495.