-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
fix(server): rework 'revoke all tokens' flow (hattorius) #4717
Conversation
Additionally, I'd like to highlight a consideration regarding the function's invocation. There is a potential benefit to removing the By eliminating the 5597666#diff-26fae77e0df373e6d5e5c8c7dc5bac72253613229222ce6e4f96262d62872f2aR901 |
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.
lgtm. simple and clean
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.
Thanks
Description
This pull request introduces a new function that plays a crucial role in the operation of the "revoke all tokens" endpoint. The primary purpose of this function is to efficiently iterate through cached authentication tokens and identify and remove all tokens associated with a specific user ID.
It's worth noting that the solution implemented here differs from the one originally discussed in the related issue. Instead, this approach aligns with the approach detailed in the Discord conversation, ensuring a more effective resolution.
Closes #4684