fix: Generate a new refresh token if an instance domain was changed#4657
Merged
fix: Generate a new refresh token if an instance domain was changed#4657
Conversation
taratatach
approved these changes
Feb 4, 2026
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
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.
After migrating an instance from one domain to another (e.g., alice.mycozy.cloud → alice.twake.app), sharings between migrated and non-migrated instances can break.
When the migration is done by:
The OAuth tokens behave as follows:
However, after a successful refresh:
This means the client continues using the old refresh token. While this works as long as OldDomain is set, it's fragile, and the refresh token should be updated to use the current domain.