fix(oauth): increase access_token and refresh_token length to 4096#22
Open
Sohail342 wants to merge 1 commit intofastapi-users:mainfrom
Open
fix(oauth): increase access_token and refresh_token length to 4096#22Sohail342 wants to merge 1 commit intofastapi-users:mainfrom
Sohail342 wants to merge 1 commit intofastapi-users:mainfrom
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.
When using OAuth2 providers such as Authentik with RS256-signed access tokens, the access_token (and sometimes refresh_token) exceeds 1024 characters. This results in a StringDataRightTruncation error in PostgreSQL:
Changes
access_tokenandrefresh_tokenfield lengths from 1024 to 4096.hatch run test.Configuration
This should allow broader compatibility with modern OAuth2 providers.