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.
Description
We implemented login.gov about a year ago. When working with login.gov the best practice is the use the login.gov user UUID as the source of truth for who the user is. However, we had to transition users off our old legacy login system and didn't know when they would all be fully transitioned. So we implemented a back up check that said "if we don't have user UUID in our database, but we do have the user email, assume it's the same user and write the UUID to that entry in the database for future use."
That transition should be complete now, so remove the email backup check.
Security Considerations
N/A