Skip to content

Commit 603e8c2

Browse files
author
katiegoines
committed
adding space to trigger tests on page
1 parent 366c059 commit 603e8c2

File tree

1 file changed

+1
-1
lines changed
  • src/pages/gen1/[platform]/build-a-backend/auth/manage-mfa

1 file changed

+1
-1
lines changed

src/pages/gen1/[platform]/build-a-backend/auth/manage-mfa/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ export function getStaticProps(context) {
3333

3434
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.
3535

36-
Before you begin, you will need:
36+
Before you begin, you will need:
3737

3838
- The Amplify libraries installed and configured
3939
- _Optional_ If you are using SMS you will need a phone number provisioned with an [SNS/Pinpoint](https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities.html)

0 commit comments

Comments
 (0)