Open
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 email verification is either off, or Parse sends verification emails each time a user signs up or changes their email address.
Our team has a custom way of onboarding users, where they verify their email addresses out-of-band.
We would like the master key to be able to bypass email verification, suppress the sending of the verification email, and mark Parse users as emailVerified=true
.
Feature / Enhancement Description
Signup requests as well as modifications to existing users where the email address is changed should not lead to a new email verification sequence, provided that the caller is the master key and the requests also sets the emailVerified
field to true.
Example Use Case
- An existing user invites a new user to their organization
- Business logic sends an invitation email
- When a link in the email is clicked, a cloud function creates a Parse user for the email that is a member of the organization to which they were invited, without sending an additional verification email.
Alternatives / Workarounds
Turning off email verification for all users, implementing custom email verification logic.
Activity
parse-github-assistant commentedon Oct 13, 2022
Thanks for opening this issue!
feat: allow the master key to bypass email verification (parse-commun…
feat: allow the master key to bypass email verification (parse-commun…
feat: allow the master key to bypass email verification (parse-commun…
mtrezza commentedon Oct 15, 2022
The feature design should consider #7144
feat: allow the master key to bypass email verification (parse-commun…
feat: allow the master key to bypass email verification (parse-commun…
mtrezza commentedon Oct 17, 2022
Maybe incorporated into #7144 (comment)
feat: allow the master key to bypass email verification (parse-commun…