When we are getting support for EMAIL_OTP challengeName, email MFA?

[gurindertrantor]

Is this related to a new or existing framework?

No response

Is this related to a new or existing API?

No response

Is this related to another service?

No response

Describe the feature you'd like to request

MFA for email was introduced by Cognito but Amplify doesn't provide support for this particular challenge name.

Describe the solution you'd like

Ideally it should support email MFA by default as it support MFA for phone number.

Describe alternatives you've considered

Ideally it should support email MFA by default as it support MFA for phone number.

Additional context

No response

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

[cwomack]

Hello, @gurindertrantor 👋 and thanks for opening this issue. Yes, we are definitely tracking this on our side and already have a feature branch (with associated PR's) that is in the works at this point. We'll update this issue as progress is made and keep anyone following informed when it's merged. Thanks!

[gurindertrantor]

Hi @cwomack and @jjarvisp any update on this? Is there any expected timeline?

Thanks!

[Mehdi-android]

Hi @cwomack and @jjarvisp what is the update? I am using this library in android kotlin
implementation("com.amplifyframework:core:1.28.0")
implementation("com.amplifyframework:aws-auth-cognito:1.28.0")

I am getting error
AuthException{message=Sign in failed, cause=java.lang.IllegalArgumentException: No enum constant com.amazonaws.mobile.client.results.SignInState.EMAIL_OTP, recoverySuggestion=See attached exception for more details.}

Give timeline please, when can we expect this issue to be resolved?

Thanks!

[cwomack]

@Mehdi-android, we try to avoid stating specific dates or time frames for when a feature is available to ensure we don't fall short of promises/expectations. That being said, I can state that this is being actively worked on and tested at this point (and I'll again point to the feature branch as something to watch 😉).

We will follow up on this issue as soon as we can with any further progress!

CC: @gurindertrantor

[sators]

Following

[smartersign]

Email MFA can't come fast enough.. thanks all for working on this!

[haverchuck]

This shipped on version 6.8.0!

[smartersign]

thanks all!

[lgolubenkobit]

Is not working for me.
Mail is received but the form to enter 2FA code is never showed.

[smartersign]

Is not working for me. Mail is received but the form to enter 2FA code is never showed.

it sounds like you are confusing the hosted UI with the amplify-js package

[lgolubenkobit]

Is not working for me. Mail is received but the form to enter 2FA code is never showed.

it sounds like you are confusing the hosted UI with the amplify-js package

We are using Amplify UI instead of Cognito UI. Some time ago we had the same error that first post.
After update to 6.8.0 error doesn't ocurr anymore but form is never showed.

[cwomack]

@lgolubenkobit, the support for Email MFA is only for the JS library at this point and not yet available for use with the Amplify UI Authenticator component. We are tracking that feature request here in the amplify-ui repo.

[lgolubenkobit]

@lgolubenkobit, the support for Email MFA is only for the JS library at this point and not yet available for use with the Amplify UI Authenticator component. We are tracking that feature request here in the amplify-ui repo.

When I read the post informing that it had been merged, I understood that the entire flow was solved. We will then wait for the solution from the amplify-ui repository.
Tranks!