3137 new token pair endpoint#3181
Merged
Merged
Conversation
08e396a to
7b68728
Compare
0806d84 to
c6c31ca
Compare
c6c31ca to
1cf264a
Compare
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #3181 +/- ##
===========================================
+ Coverage 72.50% 72.63% +0.13%
===========================================
Files 467 468 +1
Lines 13295 13344 +49
===========================================
+ Hits 9640 9693 +53
+ Misses 3655 3651 -4 see 10 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
VakarisZ
reviewed
Mar 31, 2023
VakarisZ
reviewed
Mar 31, 2023
VakarisZ
reviewed
Mar 31, 2023
VakarisZ
reviewed
Mar 31, 2023
VakarisZ
approved these changes
Mar 31, 2023
ilija-lazoroski
approved these changes
Mar 31, 2023
mssalvatore
requested changes
Mar 31, 2023
mssalvatore
left a comment
Collaborator
There was a problem hiding this comment.
I added the "needs registration" tests back in and they fail. These tests MUST be here and they MUST pass.
mssalvatore
reviewed
Mar 31, 2023
mssalvatore
reviewed
Mar 31, 2023
10 tasks
360ad96 to
f9ad76b
Compare
a95621c to
17e2755
Compare
If a new refresh token is generated, even if the old token isn't expired yet, the new one should be invalidated. We shouldn't have two valid refresh tokens for a user.
These tests were removed in the previous commit, but test security-critical portions of the authentication system. They MUST exist and they MUST pass.
All ParsedToken objects are valid at the time of creation. They have a valid signature and not be expired. Since the token may expire sometime after the object is created, `is_expired()` is provided so that other components may check expiration at a later time.
Since TokenParser will not return an invalid token, there is no longer any need to call TokenValidator.validate_token().
315c23c to
a2ce7d3
Compare
mssalvatore
approved these changes
Apr 3, 2023
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
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.
What does this PR do?
Fixes a part of #3137
PR Checklist
Was the documentation framework updated to reflect the changes?Testing Checklist
Do all end-to-end tests pass?If applicable, add screenshots or log transcripts of the feature working