-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add refresh endpoint for JWT tokens #2570
base: master
Are you sure you want to change the base?
Conversation
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2570 +/- ##
==========================================
+ Coverage 55.19% 55.69% +0.49%
==========================================
Files 561 567 +6
Lines 40917 41286 +369
==========================================
+ Hits 22584 22993 +409
+ Misses 18333 18293 -40 ☔ View full report in Codecov by Sentry. |
Now shows very clearly that you are getting exp calim or nbf claim
no longer needed for testing, found better way
doesnt actually do anything. if you set it to the past, then its valid and if you set it to the future then it will eventually be valid. setting exp to the past is enought to deactivate it for good
doesnt really add anything
a81bb92
to
f4b78a5
Compare
"data" and "body" were both used for the same thing, so changed to only use one of the terms for clarity
f4b78a5
to
67d742d
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Based on #2569
Adds an endpoint that accepts valid and active refresh tokens. The endpoint will then make a new refresh token and access token that is given to the user. This way the refresh token is only used once, limiting the risk of leaking.