Release 2.1 Changing the mechanism for saving and deleting Refresh Token #14
Conversation
This file contains 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
…er id so refresh token could be used to generate new access token even if access token is no longer available in storage
…e stored in storage instead of storing just access token value
Changed create method now store encoded tuple of RefreshTokenValue instead of access token value. Changed del method so userId will be returned even if access token is no longer available in storage.
Add fix for ramsey/uuid on PHP 8.1
composer.lockPackage changes
Settings · Docs · Powered by Private Packagist |
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.
The RefreshToken saving mechanism has been changed so that the tuple of access token and uuid is saved in the storage instead of the access token value (see RefreshTokenValueEncoder).
This way, when access keys are deleted, it will be possible to return the userId even if the access token is no longer available. As a consequence, it is possible to update the refresh/access pair when the access token is already out of date.