parse-community / parse-community/parse-server

Email confirmation on account deletion

Open
#8,025 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

type:feature
Dominant language
JavaScript
Stars
21.4k
Forks
4.8k
Avg merge
7h 45m
Merged PRs (30d)
11

Description

New Feature / Enhancement Checklist
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
  1. User request his account deletion via app.
  2. Parse-server receives the request.
  3. Parse-server sends out confirmation email to said account.
  4. User checks his email and clicks on confirmation link.
  5. Parse-server deletes the said account.
  6. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.