Improve password reset UI/UX [GCC2024_COFEST] #18467
Draft
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.
Currently, password reset uses the login name/email field as an email field and the password reset link as a submit button. This dual purpose of the login form is not intuitive and can result in confusing error messages.
This PR adds a route for password reset at /login/reset_password, accessible from the reset password link at login/start.
In addition to this, the user experience for users with an expired password has been improved by sending them directly to the password change form. Previously, the redirect sent them to /root/login which just redirected them back to /login/start, dropping the query parameters along the way. This forced them to go through the token-based password reset flow instead of the expired id + current password flow that is already supported on both the frontend and backend.
How to test the changes?
(Select all options that apply)
License