parse-community / parse-community/parse-server
Email confirmation on account deletion
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Currently, when we delete an account from the Parse.User class, there is no email confirmation option.
Feature / Enhancement Description
See: https://community.parseplatform.org/t/docs/2698/16
With Apple requiring automated account deletion on apps by July 2022, It would be good to have a secondary line of defense when we delete User objects from the data before actually going through the deletion process.
Upon calling account deletion method, much like the built in resending of verificationEmail or forgot password methods, account deletion too should have a confirmation email.
Example Use Case
- User request his account deletion via app.
- Parse-server receives the request.
- Parse-server sends out confirmation email to said account.
- User checks his email and clicks on confirmation link.
- Parse-server deletes the said account.
- Developer can have other functions in afterDelete cloudcode to remove other objects that need to be deleted.
Alternatives / Workarounds
none.
3rd Party References
no.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing Parse.User account-deletion flow and the built-in verification-email and forgot-password methods mentioned in the issue. Define the confirmation-email and confirmation-link behavior, including how deletion proceeds after confirmation, then add coverage showing that the account is deleted only after confirmation and that afterDelete behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100