One login integration migrations #10144
Draft
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.
Context
We want to allow our candidates to login into apply with one login. We also want to allow them to recover their account if their one login email is different from the candidate's email.
These are all the migrations we need for our one login integration, to allow a candidate to login or recover their account.
This is based on the one login spike
Changes proposed in this pull request
We need to allow the user to reclaim their account with any code valid in the last 1 hour for example. That's why
AccountRecoveryRequest
has_manyAccountRecoveryRequestCodes
Guidance to review
Does it make sense?
Things to check