-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
More honest reset password request response #37603
More honest reset password request response #37603
Conversation
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.
Change "administrator" to "administration".
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.
Nitpick, but nice otherwise 👍
Hi @joshtrichards please squash, rebase, run npm ci and npm run build and commit the changes here which will allow us to merge this. Thank you! |
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. Thanks!
52691cb
to
1a5700d
Compare
Addresses request in additional comments of nextcloud#37408 * Honest but still won't leak information * Also reminds user to verify the provided user id email address/user Signed-off-by: Josh Richards <josh.t.richards@gmail.com> Refine reset password response copy Co-authored-by: Louis <6653109+artonge@users.noreply.github.com> Signed-off-by: Josh Richards <josh.t.richards@gmail.com> Wrap honest password reset request response
1a5700d
to
fb25cd4
Compare
Signed-off-by: Josh Richards <josh.t.richards@gmail.com>
3f00e28
to
330c9cf
Compare
Done - theoretically. I never got it to pass the GH node workflow check 100% here in the PR (and with my latest push it's waiting on approval to run again). Since the comp'd assets get stashed in the commit it appears the GH node.yml workflow builds them again and diffs them. They always come up different than fail. Is that how it's supposed to work? Am I doing something wrong? Do they get rebuilt again during the final merge on your side? |
Summary
(Addresses feedback in additional comments of #37408)
Makes the response provided to users requesting a password reset more honest. Also reminds users to verify the provided account name or email address. Removes redundant copy. Continues to do so without leaking information.
TODO
Checklist