fix(auth): Add AuthFlowType propagation for the VerifyChallengeAnswer events #2955
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.
Issue #, if available: N/A
Description of changes: This adds AuthFlowType propagation to the VerifyChallengeAnswer events. This was missed because this doesn't really impact the actual authentication functionality but impacts the behind-the-scenes auth flow tracking. Namely, in
SignInChallengeCognitoActionswhenSignInChallengeHelper.evaluateNextStepis called, no AuthFlowType is passed in which means it fallsback to USER_SRP_AUTH.If USER_AUTH is triggered in SignIn, the ConfirmSignIn API would not have any awareness of it so we check the Amplify configuration.
HOWEVER, this does NOT cover if the user passes in the AuthFlowType into SignIn via
AWSCognitoAuthSignInOptionsHow did you test these changes? Integration tests passed -- have not done any manual testing yet
Documentation update required?
General Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.