feat: initial fix for invite followed by signup. #1262
Merged
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.
What kind of change does this PR introduce?
Currently, sending an
invite
request followed by asignup
request w/o confirmation between invite and signup will expose metadata on UserMetadata and Identities which may be perceived as a leak of sensitive information.This PR aims to clear out such metadata for cases where the dev has been invited before a signup
Testing Instructions
How to test locally:
Use this admin bearer
jwt
myemail@gmail.com
myemail@gmail.com
and check thatidentities
field is blanked out