Skip to content

Before hitting the database, check if the refresh ticket is at least 5m old and reject it or return the same token. This will help mitigate refresh loops on the client side. #48947

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.

Sign up for GitHub

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

Jump to bottom
Open
halter73 opened this issue Jun 21, 2023 · 1 comment
Open

Before hitting the database, check if the refresh ticket is at least 5m old and reject it or return the same token. This will help mitigate refresh loops on the client side. #48947

halter73 opened this issue Jun 21, 2023 · 1 comment
Labels
area-identity Includes: Identity and providers enhancement This issue represents an ask for new feature or an enhancement to an existing one
Milestone
Backlog

Comments

@halter73
Copy link
Member

halter73 commented Jun 21, 2023 •
edited
Loading

Before hitting the database, check if the refresh ticket is at least 5m old and reject it or return the same token. This will help mitigate refresh loops on the client side.

Originally posted by @Tratcher in #48595 (comment)
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically label Jun 21, 2023
@halter73 halter73 added area-identity Includes: Identity and providers and removed needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically labels Jun 21, 2023
@halter73 halter73 mentioned this issue Jun 21, 2023
Merged
@mkArtakMSFT mkArtakMSFT added the enhancement This issue represents an ask for new feature or an enhancement to an existing one label Jun 22, 2023
@mkArtakMSFT mkArtakMSFT added this to the Backlog milestone Jun 22, 2023
@ghost
Copy link

ghost commented Jun 22, 2023

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@wtgodbe wtgodbe removed the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 6, 2024
@wtgodbe wtgodbe removed the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Feb 13, 2024
@dotnet dotnet deleted a comment from dotnet-policy-service bot Feb 13, 2024
@dotnet dotnet deleted a comment from dotnet-policy-service bot Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-identity Includes: Identity and providers enhancement This issue represents an ask for new feature or an enhancement to an existing one
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@halter73 @wtgodbe @mkArtakMSFT