Manage MFA settings

The Auth category supports Multi-factor Authentication (MFA) for user sign-in flows. MFA is an extra layer of security used to make sure that users trying to gain access to an account are who they say they are. It requires users to provide additional information to verify their identity. Amplify Auth supports the MFA methods with Time-based-One-Time Passwords (TOTP) as well as text messages (SMS). In this guide we will review how you can set up MFA using TOTP and SMS and the tradeoffs between these methods to help you choose the right set up for your application. We’ll also review how to set up MFA to remember a device and reduce sign-in friction for your users.

Before you begin, you will need:

• The Amplify libraries installed and configured
• Optional If you are using SMS you will need a phone number provisioned with an SNS/Pinpoint

Enable multi-factor authentication

Below are the steps you can use to set up MFA using SMS or TOTP with the Amplify CLI. The Amplify libraries are designed to work with MFA even if you have set up your Amazon Cognito resources separately.

Understand your MFA options

When enabling MFA you will have two key decisions to make:

• MFA enforcement: As part of this setup you will determine how MFA is enforced. If you require MFA by setting MFA login to "ON", all your users will need to complete MFA to sign in. If you keep it "Optional", your users will have the choice whether to enable MFA or not for their account.
• MFA methods: You will also specify which MFA method you are using - TOTP (Time-based One-time Password), SMS (text message), or both. We recommend that you use TOTP-based MFA as it is more secure and you can reserve SMS for account recovery.

Enable MFA with the Amplify CLI

1$ amplify add auth
2
3? Do you want to use the default authentication and security configuration?
4  Manual configuration
5
6# Answer as appropriate
7
8? Multifactor authentication (MFA) user login options:
9  ON (Required for all logins, can not be enabled later)
10? For user login, select the MFA types:
11  SMS Text Message
12? Please specify an SMS authentication message:
13  Your authentication code is {####}
14
15# Answer as appropriate
16
17Some next steps:
18"amplify push" will build all your local backend resources and provision it in the cloud
19"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud

1$ amplify add auth
2
3? Do you want to use the default authentication and security configuration?
4  Manual configuration
5
6# Answer as appropriate
7
8? Multifactor authentication (MFA) user login options:
9  ON (Required for all logins, can not be enabled later)
10? For user login, select the MFA types:
11  Time-Based One-Time Password (TOTP)
12
13# Answer as appropriate
14
15Some next steps:
16"amplify push" will build all your local backend resources and provision it in the cloud
17"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud

1$ amplify update auth
2
3? What do you want to do?
4  Walkthrough all the auth configurations
5
6# Answer as appropriate
7
8? Multifactor authentication (MFA) user login options:
9  OPTIONAL (Individual users can use MFA)
10? For user login, select the MFA types:
11  SMS Text Message
12? Please specify an SMS authentication message:
13  Your authentication code is {####}
14
15# Answer as appropriate
16
17Some next steps:
18"amplify push" will build all your local backend resources and provision it in the cloud
19"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud

1$ amplify update auth
2
3? What do you want to do?
4  Walkthrough all the auth configurations
5
6# Answer as appropriate
7
8? Multifactor authentication (MFA) user login options:
9  OPTIONAL (Individual users can use MFA)
10? For user login, select the MFA types:
11  Time-Based One-Time Password (TOTP)
12
13# Answer as appropriate
14
15Some next steps:
16"amplify push" will build all your local backend resources and provision it in the cloud
17"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud

After you enable MFA you will also need to include MFA setup when users sign up. This will change depending on if you enable SMS, TOTP or both.

Multi-factor authentication with SMS

Once you have setup SMS as your second layer of authentication with MFA as shown above, your users will get an authentication code via a text message to complete sign-in after they sign in with their username and password.

If you do not have one already, you will need to configure an IAM role to use with Amazon Simple Notification Service (Amazon SNS) to manage SMS messages. You will then add this role under the "Messaging" tab for your user pool in the Amazon Cognito console. For additional information see the Amazon Cognito SMS text message MFA documentation.

Enable SMS MFA during sign-up

You will need to pass phone_number as a user attribute to enable SMS MFA for your users during sign-up. However, if the primary sign-in mechanism for your Cognito resource is phone_number (without enabling username), then you do not need to pass it as an attribute.

1import { signUp } from 'aws-amplify/auth';
2
3async function handleSignUp(
4  username: string,
5  password: string,
6  phone_number: string,
7  email: string
8) {
9  try {
10    await signUp({
11      username,
12      password,
13      options: {
14        userAttributes: {
15          phone_number,
16          email
17        }
18      }
19    });
20  } catch (error) {
21    console.log(error);
22  }
23}

1import { signUp } from 'aws-amplify/auth';
2
3async function handleSignUp(username, password, phone_number, email) {
4  try {
5    await signUp({
6      username,
7      password,
8      options: {
9        userAttributes: {
10          phone_number,
11          email
12        }
13      }
14    });
15  } catch (error) {
16    console.log(error);
17  }
18}

By default, you have to verify a user account after they sign up using the confirmSignUp API, which will send a one-time password to the user's phone number or email, depending on your Amazon Cognito configuration.

1import { confirmSignUp } from 'aws-amplify/auth';
2
3async function handleSignUpConfirmation(
4  username: string,
5  confirmationCode: string
6) {
7  try {
8    await confirmSignUp({ username, confirmationCode });
9  } catch (error) {
10    console.log(error);
11  }
12}

1import { confirmSignUp } from 'aws-amplify/auth';
2
3async function handleSignUpConfirmation(username, confirmationCode) {
4  try {
5    await confirmSignUp({ username, confirmationCode });
6  } catch (error) {
7    console.log(error);
8  }
9}

Manage SMS MFA during sign-in

After a user signs in, if they have MFA enabled for their account, a challenge will be returned that you would need to call the confirmSignIn API where the user provides their confirmation code sent to their phone number.

1import { signIn } from 'aws-amplify/auth';
2
3async function handleSignIn(username: string, password: string) {
4  try {
5    await signIn({ username, password });
6  } catch (error) {
7    console.log(error);
8  }
9}

1import { signIn } from 'aws-amplify/auth';
2
3async function handleSignIn(username, password) {
4  try {
5    await signIn({ username, password });
6  } catch (error) {
7    console.log(error);
8  }
9}

If MFA is ON or enabled for the user, you must call confirmSignIn with the OTP sent to their phone.

1import { confirmSignIn } from 'aws-amplify/auth';
2
3async function handleSignInConfirmation(otpCode: string) {
4  try {
5    await confirmSignIn({ challengeResponse: otpCode });
6  } catch (error) {
7    console.log(error);
8  }
9}

1import { confirmSignIn } from 'aws-amplify/auth';
2
3async function handleSignInConfirmation(otpCode) {
4  try {
5    await confirmSignIn({ challengeResponse: otpCode });
6  } catch (error) {
7    console.log(error);
8  }
9}

After a user has been signed in, call updateMFAPreference to record the MFA type as enabled for the user and optionally set it as preferred so that subsequent logins default to using this MFA type.

1import { updateMFAPreference } from 'aws-amplify/auth';
2
3async function handleUpdateMFAPreference() {
4  try {
5    await updateMFAPreference({ sms: 'PREFERRED' });
6  } catch (error) {
7    console.log(error);
8  }
9}

Multi-factor authentication with TOTP

You can use Time-based One-Time Password (TOTP) for multi-factor authentication (MFA) in your web or mobile applications. The Amplify Auth category includes support for TOTP setup and verification using authenticator apps, offering an integrated solution and enhanced security for your users. These apps, such as Google Authenticator, Microsoft Authenticator, have the TOTP algorithm built-in and work by using a shared secret key and the current time to generate short-lived, six digit passwords.

Set up TOTP for a user

After you initiate a user sign in with the signIn API where a user is required to set up TOTP as an MFA method, the API call will return CONTINUE_SIGN_IN_WITH_TOTP_SETUP as a challenge and next step to handle in your app. You will get that challenge if the following conditions are met:

• MFA is marked as Required in your user pool.
• TOTP is enabled in your user pool.
• User does not have TOTP MFA set up already.

The CONTINUE_SIGN_IN_WITH_TOTP_SETUP step signifies that the user must set up TOTP before they can sign in. The step returns an associated value of type TOTPSetupDetails which must be used to configure an authenticator app like Microsoft Authenticator or Google Authenticator. TOTPSetupDetails provides a helper method called getSetupURI which generates a URI that can be used, for example, in a button to open the user's installed authenticator app. For more advanced use cases, TOTPSetupDetails also contains a sharedSecret which can be used to either generate a QR code or be manually entered into an authenticator app.

Once the authenticator app is set up, the user can generate a TOTP code and provide it to the library to complete the sign in process.

1import { signIn, SignInOutput } from 'aws-amplify/auth';
2
3async function handleSignIn(username: string, password: string) {
4  try {
5    const output = await signIn({
6      username,
7      password
8    });
9
10    handleSignInNextSteps(output);
11  } catch (error) {
12    console.log(error);
13  }
14}
15
16function handleSignInNextSteps(output: SignInOutput) {
17  const { nextStep } = output;
18  switch (nextStep.signInStep) {
19    // ...
20    case 'CONTINUE_SIGN_IN_WITH_TOTP_SETUP':
21      const totpSetupDetails = nextStep.totpSetupDetails;
22      const appName = 'my_app_name';
23      const setupUri = totpSetupDetails.getSetupUri(appName);
24      // Open setupUri with an authenticator APP to retrieve an OTP code
25      break;
26    // ...
27  }
28}

1import { signIn } from 'aws-amplify/auth';
2
3async function handleSignIn(username, password) {
4  try {
5    const output = await signIn({
6      username,
7      password
8    });
9
10    handleSignInNextSteps(output);
11  } catch (error) {
12    console.log(error);
13  }
14}
15
16function handleSignInNextSteps(output) {
17  const { nextStep } = output;
18  switch (nextStep.signInStep) {
19    // ...
20    case 'CONTINUE_SIGN_IN_WITH_TOTP_SETUP':
21      const totpSetupDetails = nextStep.totpSetupDetails;
22      const appName = 'my_app_name';
23      const setupUri = totpSetupDetails.getSetupUri(appName);
24      // Open setupUri with an authenticator APP to retrieve an OTP code
25      break;
26    // ...
27  }
28}

The TOTP code can be obtained from the user via a text field or any other means. Once the user provides the TOTP code, call confirmSignIn with the TOTP code as the challengeResponse parameter.

1import { confirmSignIn } from 'aws-amplify/auth';
2
3async function handleSignInConfirmation(totpCode: string) {
4  try {
5    await confirmSignIn({ challengeResponse: totpCode });
6  } catch (error) {
7    console.log(error);
8  }
9}

1import { confirmSignIn } from 'aws-amplify/auth';
2
3async function handleSignInConfirmation(totpCode) {
4  try {
5    await confirmSignIn({ challengeResponse: totpCode });
6  } catch (error) {
7    console.log(error);
8  }
9}

After a user has been signed in, call updateMFAPreference to record the MFA type as enabled for the user and optionally set it as preferred so that subsequent logins default to using this MFA type.

1import { updateMFAPreference } from 'aws-amplify/auth';
2
3async function handleUpdateMFAPreference() {
4  try {
5    await updateMFAPreference({ totp: 'PREFERRED' });
6  } catch (error) {
7    console.log(error);
8  }
9}

Enable TOTP after a user is signed in

TOTP MFA can be set up after a user has signed in. This can be done when the following conditions are met:

• MFA is marked as Optional or Required in your user pool.
• TOTP is marked as an enabled MFA method in your user pool.

TOTP can be set up by calling the setUpTOTP and verifyTOTPSetup APIs in the Auth category.

Invoke the setUpTOTP API to generate a TOTPSetupDetails object which should be used to configure an Authenticator app like Microsoft Authenticator or Google Authenticator. TOTPSetupDetails provides a helper method called getSetupURI which generates a URI that can be used, for example, in a button to open the user's installed Authenticator app. For more advanced use cases, TOTPSetupDetails also contains a sharedSecret which can be used to either generate a QR code or be manually entered into an Authenticator app.

that contains the sharedSecret which will be used to either to generate a QR code or can be manually entered into an Authenticator app.

1import { setUpTOTP } from 'aws-amplify/auth';
2
3async function handleTOTPSetup() {
4  try {
5    const totpSetupDetails = await setUpTOTP();
6    const appName = 'my_app_name';
7    const setupUri = totpSetupDetails.getSetupUri(appName);
8    // Open setupUri with an authenticator APP to retrieve an OTP code
9  } catch (error) {
10    console.log(error);
11  }
12}

Once the Authenticator app is set up, the user must generate a TOTP code and provide it to the library. Pass the code to verifyTOTPSetup to complete the TOTP setup process.

1import { verifyTOTPSetup } from 'aws-amplify/auth';
2
3async function handleTOTPVerification(totpCode: string) {
4  try {
5    await verifyTOTPSetup({ code: totpCode });
6  } catch (error) {
7    console.log(error);
8  }
9}

1import { verifyTOTPSetup } from 'aws-amplify/auth';
2
3async function handleTOTPVerification(totpCode) {
4  try {
5    await verifyTOTPSetup({ code: totpCode });
6  } catch (error) {
7    console.log(error);
8  }
9}

After TOTP setup is complete, call updateMFAPreference to record the MFA type as enabled for the user and optionally set it as preferred so that subsequent logins default to using this MFA type.

1import { updateMFAPreference } from 'aws-amplify/auth';
2
3async function handleUpdateMFAPreference() {
4  try {
5    await updateMFAPreference({ sms: 'ENABLED', totp: 'PREFERRED' });
6  } catch (error) {
7    console.log(error);
8  }
9}

Recover from a lost TOTP device

In a scenario where MFA is marked as "Required" in the Cognito User Pool and another MFA method is not set up, the administrator would need to first initiate an AdminUpdateUserAttributes call and update the user’s phone number attribute. Once this is complete, the administrator can continue changing the MFA preference to SMS as suggested above.

Set up a user's preferred MFA method

Fetch the current user's MFA preferences

Invoke the following API to get the current MFA preference and enabled MFA types, if any, for the current user.

1import { fetchMFAPreference } from 'aws-amplify/auth';
2
3async function handleFetchMFAPreference() {
4  try {
5    const output = await fetchMFAPreference();
6    console.log(`Enabled MFA types for the user: ${output.enabled}`);
7    console.log(`Preferred MFA type for the user: ${output.preferred}`);
8  } catch (error) {
9    console.log(error);
10  }
11}

Update the current user's MFA preferences

Invoke the following API to update the MFA preference for the current user.

1import { updateMFAPreference } from 'aws-amplify/auth';
2
3async function handleUpdateMFAPreference() {
4  try {
5    await updateMFAPreference({ sms: 'ENABLED', totp: 'PREFERRED' });
6  } catch (error) {
7    console.log(error);
8  }
9}

If multiple MFA methods are enabled for the user, the signIn API will return CONTINUE_SIGN_IN_WITH_MFA_SELECTION as the next step in the auth flow. During this scenario, the user should be prompted to select the MFA method they want to use to sign in and their preference should be passed to confirmSignIn.

1import { confirmSignIn, SignInOutput } from 'aws-amplify/auth';
2
3function handleSignInNextSteps(output: SignInOutput) {
4  const { nextStep } = output;
5  switch (nextStep.signInStep) {
6    // ...
7    case 'CONTINUE_SIGN_IN_WITH_MFA_SELECTION':
8      const allowedMFATypes = nextStep.allowedMFATypes;
9      const mfaType = promptUserForMFAType(allowedMFATypes);
10    case 'CONFIRM_SIGN_IN_WITH_SMS_CODE':
11      // display user to enter otp code;
12      break;
13    case 'CONFIRM_SIGN_IN_WITH_TOTP_CODE':
14      // display user to enter otp code;
15      break;
16    // ...
17  }
18}
19
20function promptUserForMFAType(
21  allowedMFATypes?: ('SMS' | 'TOTP')[]
22): 'SMS' | 'TOTP' {
23  // Prompt user to select MFA type
24}
25
26async function handleMFASelection(mfaType: 'SMS' | 'TOTP') {
27  try {
28    const output = await confirmSignIn({
29      challengeResponse: mfaType
30    });
31    handleSignInNextSteps(output);
32  } catch (error) {
33    console.log(error);
34  }
35}

1function handleSignInNextSteps(output) {
2  const { nextStep } = output;
3  switch (nextStep.signInStep) {
4    // ...
5    case 'CONTINUE_SIGN_IN_WITH_MFA_SELECTION':
6      const allowedMFATypes = nextStep.allowedMFATypes;
7      const mfaType = promptUserForMFAType(allowedMFATypes);
8    case 'CONFIRM_SIGN_IN_WITH_SMS_CODE':
9      // display user to enter otp code;
10      break;
11    case 'CONFIRM_SIGN_IN_WITH_TOTP_CODE':
12      // display user to enter otp code;
13      break;
14    // ...
15  }
16}
17
18function promptUserForMFAType(allowedMFATypes) {
19  // Prompt user to select MFA type
20}
21
22async function handleMFASelection(mfaType) {
23  try {
24    const output = await confirmSignIn({
25      challengeResponse: mfaType
26    });
27    handleSignInNextSteps(output);
28  } catch (error) {
29    console.log(error);
30  }
31}

Remember a device

Remembering a device is useful in conjunction with MFA because it allows the second factor requirement to be automatically met when your user signs in on that device and reduces friction in their sign-in experience.

Configure device tracking

You can enable the remembered device functionality in the Cognito User Pool console. To begin, go to your project directory and issue the command:

1amplify auth console

Select the following option to open the Cognito User Pool console:

1? Which Console
2    User Pool

When the console opens, scroll down to the "Device Tracking" section and select the "Edit" button. This will render the following page allowing you to configure your preference for remembering a user's device.

Choose either "Always remember" to remember a user's device by default or "User Opt-in" to give the user the ability to choose.

When MFA is enabled you will have the option to suppress the second factor during multi-factor authentication. Choose "Yes" if you want a remembered device to be used as a second factor mechanism.

When you have made your selection(s), click "Save changes". You are now ready to start updating your code to manage remembered devices.

Remember devices

You can remember devices using the following:

1import { rememberDevice } from 'aws-amplify/auth';
2
3export async function handleRememberDevice() {
4  try {
5    await rememberDevice();
6  } catch (error) {
7    console.log(error);
8  }
9}

1import { rememberDevice } from 'aws-amplify/auth';
2
3export async function handleRememberDevice() {
4  try {
5    await rememberDevice();
6  } catch (error) {
7    console.log(error);
8  }
9}

Forget devices

You can also forget devices but note that forgotten devices are neither remembered nor tracked.

1import { forgetDevice } from 'aws-amplify/auth';
2
3export async function handleForgetDevice() {
4  try {
5    await forgetDevice();
6  } catch (error) {
7    console.log(error);
8  }
9}

1import { forgetDevice } from 'aws-amplify/auth';
2
3export async function handleForgetDevice() {
4  try {
5    await forgetDevice();
6  } catch (error) {
7    console.log(error);
8  }
9}

Fetch devices

You can fetch a list of remembered devices by using the following:

1import { fetchDevices } from 'aws-amplify/auth';
2
3export async function handleFetchDevices() {
4  try {
5    const output = await fetchDevices();
6    console.log(output);
7  } catch (error) {
8    console.log(error);
9  }
10}

1import { fetchDevices } from 'aws-amplify/auth';
2
3async function handleFetchDevices() {
4  try {
5    const output = await Auth.fetchDevices();
6    console.log(output);
7  } catch (error) {
8    console.log(error);
9  }
10}

You can now set up devices to be remembered, forgotten, and fetched.

Conclusion

Congratulations! You finished the Manage MFA settings guide. In this guide, you set up and configured MFA for your users and provided them options on remembering their MFA preferences and devices.

Next steps

Now that you completed setting up multi-factor authentication you may also want to add additional customization. We recommend you learn more about:

• Switching authentication flows
• Advanced workflows