You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is not built-in workflow for changing an email address like there is for email verification or password reset.
Feature / Enhancement Description
Adding a built-in workflow for changing the email address can leverage the already existing mechanisms for email verification / password reset.
Example Use Case
User requests to change the email.
Parse Server sends email to old email address.
User opens email link and gets to website to enter a new email address.
Parse Server changes email address in DB and sends confirmation email to old and new email address.
Alternatives / Workarounds
Manually implementing a workflow.
3rd Party References
(none)
Note
Before anyone starts to work on a PR, it makes sense to wait until the new PagesRouter is merged where this kind of workflow is easier to implement. In addition, any implementation in the current PublicAPIRouter will become obsolete once the PagesRouter goes out of experimental state - which should be fairly soon.
The text was updated successfully, but these errors were encountered:
Yes, the Pages Router is capable of building this, but it is currently only available on the master branch and will be available from Parse Server 5.0. We are planning to release a 5.0 beta version in September.
But even with Parse Server 5.0 there won't be a built-in flow to change the email address, it still has to be built manually, but that will be quite easy and take only a handful of lines of code.
New Feature / Enhancement Checklist
Current Limitation
Currently there is not built-in workflow for changing an email address like there is for email verification or password reset.
Feature / Enhancement Description
Adding a built-in workflow for changing the email address can leverage the already existing mechanisms for email verification / password reset.
Example Use Case
Alternatives / Workarounds
Manually implementing a workflow.
3rd Party References
(none)
Note
Before anyone starts to work on a PR, it makes sense to wait until the new PagesRouter is merged where this kind of workflow is easier to implement. In addition, any implementation in the current PublicAPIRouter will become obsolete once the PagesRouter goes out of experimental state - which should be fairly soon.
The text was updated successfully, but these errors were encountered: