Add test case for refresh token flow with jwt #17
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
This was referenced Aug 6, 2017
|
Merging! Will bump the pre-reqs and then upload to CPAN. Thanks! |
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.
Refresh token is not working as expected with JWT, after a refresh, the client element of the JWT is containing the full previous refresh token, instead of the client only.
I just added a test case here, it's breaking, and i have "solution proposal" under 'net-oauth2-authorizationserver' in another pull request, however, i'm not certain if there is any unexpected behaviour in some edge cases, but all the unit test continue to pass with the proposed solution, on theother repo