[codex] Fix social login token storage#267
Merged
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.
What changed
user.social_login_tokentoLONGTEXT.User.socialLoginTokenJPA mapping to match the migrated schema.Why
Google and Apple OAuth refresh tokens can exceed 255 characters. The existing
VARCHAR(255)column caused Google login to fail withData truncation: Data too long for column 'social_login_token'when saving a user during login.Impact
OAuth login can persist provider refresh tokens without truncation errors. Production logs will also stop emitting raw credential material on login/token issuance paths.
Validation
./gradlew compileJavapasses../gradlew testcompiles but cannot complete locally because the Spring test context attempts to connect to MySQL atlocalhost:3306, which is not running in this workspace.