Fix assigning TrnVerificationLevel for new users #772
Merged
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
gunndabad
force-pushed
the
fix-trnverificationlevel-for-aytq-registrations
branch
2 times, most recently
from
28ee4e1 to
9561c7e
Compare
gunndabad
force-pushed
the
fix-trnverificationlevel-for-aytq-registrations
branch
from
9561c7e to
bbde595
Compare
MrKevJoy
approved these changes
Dec 5, 2023
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.
AYTQ has been blowing up for some users with a 403 from the API. After some debugging we find the access token is missing the
trnclaim. The logic that adds thetrnclaim omitted it because theUser'sTrnVerificationLevelwas set asLow(and the journey requiresMedium), even though they've gone through a journey that should set it toMedium.This fixes the user creation logic to correctly assign
TrnVerificationLevel. It also adds a migration to fix up the data for the users who have encountered this.