[13.x] Fix determining revoked records #1751
Merged
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.
This PR fixes how we determine if the specified record is revoked and adds integration tests for this.
Auth Code
If the given auth code does not exist (removed),
Bridge/AuthCodeRepository::isAuthCodeRevoked()
returnsfalse
mistakenly.Access Token
TokenRepository::isAccessTokenRevoked()
is usingfind
to determine if the given access token is revoked, this causes performance issue asTokenGaurd
callsfind
twice on every request.Refresh Token
RefreshTokenRepository::isRefreshTokenRevoked()
also usesfind
to determine if the given refresh token is revoked.