Details
-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
2.7.7
-
None
-
None
-
Magnolia Demo
Description
Steps to reproduce
- add a front end user
- request a password reset token (forgot password functionality
- on the password change page, enter a password that does not meet the password requirements
- hit send
- after return to page with error, try again with password that meets requirements
- error: tokenpasswordprocessor.user.not.exist
.. Logs, screenshots, gifs...
Expected results
the password is being set
.. Justify non-trivial expectations with a link to a doc or a relevant discussion.
Actual results
error leads to a situation the user may be unable to resolve by themselves (i.e. opening the link from the email again)
Workaround
extend the form field and add a front end pattern so that there is a html 5 form validation that catches the problem in browser
Development notes
the change password functionality uses the standard form module with a different processor - as with all forms if it comes back with an error you only have the mgnlFormToken attached as a parameter - the code for the password change relies on the userId and token parameters to be present though.
Checklists
Acceptance criteria