-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-3570] Adjust refresh token lifetimes #3697
Conversation
Test Before this lands we have to confirm that all clients are re-storing the returned refresh token. We think that was the case but weren't sure 100%. Additionally, is there any risk of hardcoded lifetimes in the clients? |
Looks like its doing some new functionality with onetime use. I see it trying to delete the old token from the grant store after it creates the new one. Cool.
|
No New Or Fixed Issues Found |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3697 +/- ##
==========================================
- Coverage 39.32% 38.82% -0.50%
==========================================
Files 1032 1034 +2
Lines 51056 51105 +49
Branches 4581 4577 -4
==========================================
- Hits 20076 19843 -233
- Misses 30036 30330 +294
+ Partials 944 932 -12 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change makes sense to me. Let's ensure client compliance before we merge anything.
We'll want to ensure this acts as expected with our Cosmos store too, and meeting performance expectations for deletes.
Type of change
Objective
Adjusting token lifetimes to be in line with normal use cases.
Fix grant delete implementation for EF.
Code changes
Before you submit
dotnet format --verify-no-changes
) (required)