Password Reset UI #213

Closed
opened 2018-12-12 17:29:11 +00:00 by i1t · 8 comments
Member

FE part of pleroma/pleroma#114

(This spec is WIP, additions / changes are very welcome)

Password Reset

  • Add a new form containing email field and submit button (clarify whether we need to use nickname instead of email — BE supports both, see pleroma/pleroma#3924)
  • Add navigation to that form ("Forgot password?" link next to Register link in Login form? We don't seem to have it in current translations, though)
  • On submit, do POST to /api/account/password_reset (note: email parameter takes precedence over nickname on BE)
  • On 204 No Content, redirect to login form (main screen) -or- display "Password reset link sent!" message (prevent submitting the form more than once for unauthenticated users, though admins might want to submit it numerous times for different users — TBD)
  • On error response, display the error

Post-registration changes

  • Only if /statusnet/config has accountActivationRequired set to 1, display message that user needs to check mailbox for account confirmation email prior to logging in (clarify the exact wording). Also, registration action will render pleroma.confirmation_pending as true in this case (see pleroma/pleroma#3939).

P.S. "Invite via Email" part moved to #192

FE part of https://git.pleroma.social/pleroma/pleroma/issues/114 (This spec is WIP, additions / changes are very welcome) ## Password Reset * Add a new form containing `email` field and submit button (clarify whether we need to use `nickname` instead of `email` — BE supports both, see https://git.pleroma.social/pleroma/pleroma/pulls/3924) * Add navigation to that form ("Forgot password?" link next to Register link in Login form? We don't seem to have it in current translations, though) * On submit, do POST to `/api/account/password_reset` (note: `email` parameter takes precedence over `nickname` on BE) * On `204 No Content`, redirect to login form (main screen) -or- display "Password reset link sent!" message (prevent submitting the form more than once for unauthenticated users, though admins might want to submit it numerous times for different users — TBD) * On error response, display the error ## Post-registration changes * Only if `/statusnet/config` has `accountActivationRequired` set to `1`, display message that user needs to check mailbox for account confirmation email prior to logging in (clarify the exact wording). Also, registration action will render `pleroma.confirmation_pending` as `true` in this case (see https://git.pleroma.social/pleroma/pleroma/pulls/3939). P.S. "Invite via Email" part moved to https://git.pleroma.social/pleroma/pleroma-fe/issues/192#note_10034
Author
Member

We might also need admin UI for generating password reset email for another user. The password reset form is going to stay the same (I believe) but navigation to it would be different (TBD).

We might also need admin UI for generating password reset email for another user. The password reset form is going to stay the same (I believe) but navigation to it would be different (TBD).
Member

Invite via email should be part of #192 for now because only admins/mods can make invites atm.

Invite via email should be part of #192 for now because only admins/mods can make invites atm.
Member

On 204 No Content, redirect to login form (main screen)

I'd rather not redirect anywhere but show "Password reset link sent!" instead.

>On `204 No Content`, redirect to login form (main screen) I'd rather not redirect anywhere but show "Password reset link sent!" instead.
Author
Member

@HJ, should we move email invitation part to #192 or keep it here? If moving, would a comment do, or should I ask #192's author to edit the description?

@HJ, should we move email invitation part to #192 or keep it here? If moving, would a comment do, or should I ask #192's author to edit the description?
Author
Member

@hj, no issues with displaying the message instead, but some users might leave it unnoticed and submit the form again. Let's prevent submitting it more than once on 2xx response.

@hj, no issues with displaying the message instead, but some users might leave it unnoticed and submit the form again. Let's prevent submitting it more than once on 2xx response.
Member

Let's prevent submitting it more than once on 2xx response.

disabling form entry is a thing

>Let's prevent submitting it more than once on 2xx response. disabling form entry is a thing
Member

If moving, would a comment do

a comment would do.

>If moving, would a comment do a comment would do.
Member

I just lost my password and really wish this feature was done. Sadly, I don't know much JavaScript at all, so I don't think I can be of much use contributing code. Is there anything left to discuss about the above spec? It seems reasonable to me as-is.

I just lost my password and really wish this feature was done. Sadly, I don't know much JavaScript at all, so I don't think I can be of much use contributing code. Is there anything left to discuss about the above spec? It seems reasonable to me as-is.
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pleroma/pleroma-fe#213
No description provided.