-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
UX + Security current user password reset #5042
UX + Security current user password reset #5042
Conversation
c483c86
to
f8cf890
Compare
Codecov Report
@@ Coverage Diff @@
## master #5042 +/- ##
=========================================
Coverage ? 41.66%
=========================================
Files ? 414
Lines ? 55985
Branches ? 0
=========================================
Hits ? 23327
Misses ? 29529
Partials ? 3129
Continue to review full report at Codecov.
|
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.
I'm against auto-signin on password reset. Consequently I find having "Remember me" on Password reset awkward.
IMO we need a "password confirmation" field instead.
Showing Email is fine.
4594723
to
c8dcf9e
Compare
@daviian The "Remember me" felt a little weird to me too. What I came to was that it's actually the form was incorrectly labeled. "Password Reset" is the process that happens on the Account page. This process is actually "Account Recovery", which is a different user flow. The user isn't coming to this page with the intent to change their password (that is already on the Account page), but rather to be able to login to their account. In this case, with the current configuration, that implicitly includes setting a password. However, once more secure options are available (such as simply omitting passwords if a mailer is configured) the user will still want to recover their account (i.e. their primary oauth is down and they can't log in) but a password won't be part of the process. I'll post new screenshots a little later. |
Two more things that should change for increased clarity:
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 months. Thank you for your contributions. |
I'm back on the scene. I'll see what I can do to get this stuff cleaned up and PR'd again. |
9334293
to
3839984
Compare
Rebased and ready for re-review! |
@@ -273,8 +273,6 @@ func RegisterRoutes(m *macaron.Macaron) { | |||
}, openIDSignInEnabled) | |||
m.Get("/sign_up", user.SignUp) | |||
m.Post("/sign_up", bindIgnErr(auth.RegisterForm{}), user.SignUpPost) | |||
m.Get("/reset_password", user.ResetPasswd) |
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.
Do we need to atleast redirect to the new route before this is finally removed in 1.10?
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.
@adelowo I don't see why as emails having old route won't be usable anyway as code is valid only for few hours
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.
Ha true... stupid me
@daviian need your approval |
Follow up to #5034
I'll annotate these a little later, but it's combos for these states:
Default Condition
Result
Logged In
Result
Invalid Code
Result
Invalid User
Result