Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amplify does not expose the challenge response values for MFA selection #2677

Closed
1 task done
mattcreaser opened this issue Jan 9, 2024 · 2 comments
Closed
1 task done
Assignees
Labels
auth Related to the Auth category/plugins bug Something isn't working

Comments

@mattcreaser
Copy link
Contributor

Before opening, please confirm:

Language and Async Model

Not applicable

Amplify Categories

Authentication

Gradle script dependencies

// Put output below this line

Environment information

# Put output below this line


Please include any relevant guides or documentation you're referencing

No response

Describe the bug

When multiple MFA methods (i.e. SMS + TOTP) are enabled in Cognito, Amplify will return a next sign in step of CONTINUE_SIGN_IN_WITH_MFA_SELECTION and pass back a set of allowed MFA types: allowedMFATypes: Set<MFAType>.

The intended use is that the user will chose one of these types, and then the application will call confirmSignIn(challengeResponse) to continue the sign in process.

The issue is that the value of challengeResponse that needs to be passed is one of either "SMS_MFA" or "SOFTWARE_TOKEN_MFA", and these aren't exposed anywhere in the Amplify API or documented in the public documentation (that I can find).

On Swift, these values are available by calling e.g. selectedMfaType.challengeResponse.

Reproduction steps (if applicable)

No response

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line


amplifyconfiguration.json

No response

GraphQL Schema

// Put your schema below this line

Additional information and screenshots

No response

@mattcreaser mattcreaser added bug Something isn't working auth Related to the Auth category/plugins labels Jan 9, 2024
@mattcreaser mattcreaser self-assigned this Jan 11, 2024
@mattcreaser mattcreaser added the pending-release Code has been merged but pending release label Jan 19, 2024
@mattcreaser
Copy link
Contributor Author

This has been released in Amplify 2.14.10 🎉

@mattcreaser mattcreaser removed the pending-release Code has been merged but pending release label Feb 8, 2024
Copy link
Contributor

github-actions bot commented Feb 8, 2024

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auth Related to the Auth category/plugins bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant