Handle replication lag when authenticating with a Bearer Token #1922
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.
Changes / Features implemented
MasterReplicaOAuth2Validator
classMasterReplicaOAuth2Validator
as the OAuth2 Request validatorUserProfile
from main database on failureSteps taken to verify this change does what is intended
Side effects of implementing this change
AccessToken
from the read replica, the application will now try to retrieve theAccessToken
from the master database.Closes #1920