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.

Sign up for GitHub

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

Jump to bottom

fix heading levels #7906

Merged
merged 2 commits into from
Aug 21, 2024
Merged

fix heading levels #7906

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
366c059
fix heading levels
Aug 21, 2024
603e8c2
adding space to trigger tests on page
Aug 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/fragments/lib/auth/common/mfa/add_mfa.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
#### SMS MFA
### SMS MFA
```bash
$ amplify add auth

Expand All @@ -21,7 +21,7 @@ Some next steps:
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud
```

#### TOTP MFA
### TOTP MFA
```bash
$ amplify add auth

Expand All @@ -40,4 +40,4 @@ $ amplify add auth
Some next steps:
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud
```
```
6 changes: 3 additions & 3 deletions src/fragments/lib/auth/common/mfa/update_mfa.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ The following steps show how to enable MFA as "Optional" for users. In this mode

If you'd like to make MFA required for users, you must first delete your auth resource by running `amplify remove auth`, then follow the **New Project** flow on this page.

#### SMS MFA
### SMS MFA
```bash
$ amplify update auth

Expand All @@ -27,7 +27,7 @@ Some next steps:
```


#### TOTP MFA
### TOTP MFA
```bash
$ amplify update auth

Expand All @@ -46,4 +46,4 @@ $ amplify update auth
Some next steps:
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud
```
```
2 changes: 1 addition & 1 deletion src/pages/gen1/[platform]/build-a-backend/auth/manage-mfa/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ export function getStaticProps(context) {

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:
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](https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities.html)
Expand Down
Loading