Skip to content
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

Block user after a refresh failure #485

Closed
d-fischer opened this issue Apr 2, 2023 · 0 comments
Closed

Block user after a refresh failure #485

d-fischer opened this issue Apr 2, 2023 · 0 comments
Labels
improvement semver-major Issues that need a major version bump to be released (i.e. a breaking change)
Milestone
7.0

Comments

@d-fischer
Copy link
Member

When RefreshingAuthProvider receives a request to refresh a token and then fails to do so, it should block all subsequent calls to fetch or refresh a token for that user with a custom error class in order to ensure that no useless API requests are made.

Only a call to addUser or addUserForToken that resolves to that user can unlock them.
@d-fischer d-fischer added improvement semver-major Issues that need a major version bump to be released (i.e. a breaking change) labels Apr 2, 2023
@d-fischer d-fischer added this to the 7.0 milestone Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement semver-major Issues that need a major version bump to be released (i.e. a breaking change)
Projects
None yet
Milestone
7.0
Development

No branches or pull requests
1 participant
@d-fischer