[login] Rework reset password functionality#10977
Open
HachemJ wants to merge 11 commits into
Open
Conversation
Collaborator
|
@HachemJ Can you send this to main instead of 29? I think it's too late in the release testing to incorporate a change this significant |
Contributor
Author
Sure |
HachemJ
force-pushed
the
ReworkResetPasswordFunctionality
branch
from
July 22, 2026 16:24
bebd151 to
b7f347a
Compare
…is expired or invalid, change query to find count directly instead of using count function on array and reset ALL valid reset tokens when the password was successfully updated
… form is submitted, clean up expired token when reset password form is submitted if older than 20 minutes
HachemJ
force-pushed
the
ReworkResetPasswordFunctionality
branch
from
July 22, 2026 16:38
b7f347a to
0f013da
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brief summary of changes
This PR redesigns the password reset workflow by removing the legacy password expiration mechanism and replacing it with a token lifecycle managed through
user_password_reset.Changes
PasswordChangeRequiredfrom the schema and backend.NULL,Used,Superseded).Usedand invalidate remaining active tokens asSuperseded.Testing instructions (if applicable)