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
It's currently not possible to verify a user password if email verification is required and the user's email has not been verified. Even when using the master key, a request to REST API /verifyPassword fails with Parse error 205.
Feature / Enhancement Description
Introduce new request option ignoreEmailVerification that together with the master or maintenance key allows to verify a user password ignoring the email verification status.
Example Use Case
It may be necessary to verify a user password irrespective of email verification status, for example to allow a user to change an incorrectly entered email that could not be verified because it is incorrect. A developer can write a Cloud Function that does just that.
Alternatives / Workarounds
Use maintenance key and compare hashed passwords, which is discouraged for many reasons.
The text was updated successfully, but these errors were encountered:
New Feature / Enhancement Checklist
Current Limitation
It's currently not possible to verify a user password if email verification is required and the user's email has not been verified. Even when using the master key, a request to REST API
/verifyPassword
fails with Parse error 205.Feature / Enhancement Description
Introduce new request option
ignoreEmailVerification
that together with the master or maintenance key allows to verify a user password ignoring the email verification status.Example Use Case
It may be necessary to verify a user password irrespective of email verification status, for example to allow a user to change an incorrectly entered email that could not be verified because it is incorrect. A developer can write a Cloud Function that does just that.
Alternatives / Workarounds
Use maintenance key and compare hashed passwords, which is discouraged for many reasons.
The text was updated successfully, but these errors were encountered: