Invalidate all tokens when email changes #9855
Draft
Conversation
This file contains 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
Betree
force-pushed
the
enhancement/token-payload-email
branch
from
89c2c36
to
2e4b531
Compare
Betree
commented
Feb 28, 2024
znarf
reviewed
Feb 28, 2024
Betree
force-pushed
the
enhancement/token-payload-email
branch
from
f672f7c
to
4341f69
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Goes with opencollective/opencollective-frontend#10379
Implemented by introducing a new
confirmEmailmutation on GraphQL V2 (rather than using the V1 mutation) to prevent breaking changes when deploying. As a result, old frontends will be logged out after successfully changing the email.Todo: