-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
fix: Remove username from email verification and password reset process #8488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 33 commits
Commits
Show all changes
35 commits
Select commit
Hold shift + click to select a range
78c67d4
fix: remove username from verification emails
dblythy 407825d
tests
dblythy 0c49a4a
feat: allow Pointers in cloud code params
dblythy 3d50b00
Revert "feat: allow Pointers in cloud code params"
dblythy 713e357
Merge branch 'alpha' into password-reset
dblythy f814457
wip
dblythy b960a1a
Update ValidationAndPasswordsReset.spec.js
dblythy 9f3808a
Merge remote-tracking branch 'upstream/alpha' into password-reset
dblythy 9d4a028
Update UserController.spec.js
dblythy 7252893
fix failing tests
dblythy f9b54dd
Update UserController.js
dblythy 4a72e2e
fix tests
dblythy e110732
Update ValidationAndPasswordsReset.spec.js
dblythy 5beb30f
Update ValidationAndPasswordsReset.spec.js
dblythy 205d59e
Update UserController.spec.js
dblythy db5409a
fix failing tests
dblythy 170f83a
add logging
dblythy 6ff9e6b
Update CurrentSpecReporter.js
dblythy e1ed76b
revert resolve
dblythy 0d8a4a2
add catch
dblythy 493fcf2
Merge branch 'alpha' into password-reset
dblythy 0cb359a
Merge branch 'alpha' into password-reset
mtrezza 3295166
Create 8.0.0.md
dblythy 4808c8a
fix pages router
dblythy c09bc87
Merge branch 'alpha' into password-reset
mtrezza d60bbd2
review feedback
dblythy e6b67ed
Update 8.0.0.md
mtrezza 780bc48
Update 8.0.0.md
mtrezza 42a2ff5
Update 8.0.0.md
mtrezza a32d0e6
Update 8.0.0.md
mtrezza ae6ac40
Merge branch 'alpha' into password-reset
mtrezza e75113c
Update 8.0.0.md
mtrezza 02069d9
Update 8.0.0.md
dblythy 280984f
Update 8.0.0.md
mtrezza e0e094c
Merge branch 'alpha' into password-reset
mtrezza File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # Parse Server 8 Migration Guide <!-- omit in toc --> | ||
|
|
||
| This document only highlights specific changes that require a longer explanation. For a full list of changes in Parse Server 8 please refer to the [changelog](https://github.com/parse-community/parse-server/blob/alpha/CHANGELOG.md). | ||
|
|
||
| --- | ||
|
|
||
| - [Email Verification](#email-verification) | ||
|
|
||
| --- | ||
|
|
||
| ## Email Verification | ||
|
|
||
| In order to remove sensitive information (PII) from technical logs, the `Parse.User.username` field has been removed from the email verification process. This means the username will no longer be used and the already existing verification token, that is internal to Parse Server and associated with the user, will be used instead. This makes use of the fact that an expired verification token is not deleted from the database by Parse Server, despite being expired, and can therefore be used to identify a user. | ||
|
|
||
| This change affects how verification emails with expired tokens are handled. When opening a verification link that contains an expired token, the page that the user is redirected to will no longer provide the `username` as a URL query parameter. Instead, the URL query parameter `token` will be provided. | ||
|
|
||
| The request to re-send a verification email changed to sending a `POST` request to the endpoint `/resend_verification_email` with `token` in the body, instead of `username`. If you have customized the HTML pages for email verification either for the `PagesRouter` in `/public/` or the deprecated `PublicAPIRouter` in `/public_html/`, you need to adapt the form request in your custom pages. See the example pages in these aforementioned directories for how the forms must be set up. | ||
|
|
||
| > [!WARNING] | ||
| > An expired verification token is not automatically deleted from the database by Parse Server even though it has expired. If you have implemented a custom clean-up logic that removes expired tokens, this will break the form request to re-send a verification email as the expired token won't be found and cannot be associated with any user. In that case you'll have to implement your custom process to re-send a verification email. | ||
| > The resend mechanism is only comptabile with the most recent expired database. It is recommended to use `emailVerifyTokenReuseIfValid` to reduce the likelihood of having to deal with expired tokens. | ||
|
|
||
| Related pull requests: | ||
|
|
||
| - https://github.com/parse-community/parse-server/pull/8488 | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.