Skip to content

Commit b313965

Browse files
committed
tweak language
1 parent 014b305 commit b313965

File tree

1 file changed

+6
-6
lines changed
  • src/pages/[platform]/build-a-backend/auth/connect-your-frontend/multi-step-sign-in

1 file changed

+6
-6
lines changed

src/pages/[platform]/build-a-backend/auth/connect-your-frontend/multi-step-sign-in/index.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -402,7 +402,7 @@ async function confirmWithPassword(password: string) {
402402

403403
## Continue sign-in with First Factor Selection
404404

405-
If the next step is `CONTINUE_SIGN_IN_WITH_FIRST_FACTOR_SELECTION`,the user must select a first factor method for authentication. After the user selects an option, your implementation should pass the selected method to the `confirmSignIn` API.
405+
If the next step is `CONTINUE_SIGN_IN_WITH_FIRST_FACTOR_SELECTION`, the user must select a first factor method for authentication. After the user selects an option, your implementation should pass the selected method to the `confirmSignIn` API.
406406

407407
The first factor types which are currently supported by Amplify Auth are:
408408
- `SMS_OTP`
@@ -413,12 +413,12 @@ The first factor types which are currently supported by Amplify Auth are:
413413

414414
Depending on your configuration and what factors the user has previously setup, not all options may be available. Only the available options will be presented in `availableChallenges` for selection.
415415

416-
Once Amplify receives the users selection, you can expect to handle a follow up `nextStep` corresponding with the selected factor type:
417-
418-
- If `SMS_OTP` is selected, you can expect to receive `CONFIRM_SIGN_IN_WITH_SMS_CODE` as the next step.
419-
- If `EMAIL_OTP` is selected, you can expect to receive `CONFIRM_SIGN_IN_WITH_EMAIL_CODE` as the next step.
420-
- If `WEB_AUTHN` is selected, Amplify will initiate the authentication ceremony on the user's device. If successful, the next step will be `DONE`.
416+
Once Amplify receives the user's selection via the `confirmSignIn` API, you can expect to handle a follow up `nextStep` corresponding with the first factor type selected:
417+
- If `SMS_OTP` is selected, `CONFIRM_SIGN_IN_WITH_SMS_CODE` will be the next step.
418+
- If `EMAIL_OTP` is selected, `CONFIRM_SIGN_IN_WITH_EMAIL_CODE` will be the next step.
421419
- If `PASSWORD` or `PASSWORD_SRP` is selected, `CONFIRM_SIGN_IN_WITH_PASSWORD` will be the next step.
420+
- If `WEB_AUTHN` is selected, Amplify Auth will initiate the authentication ceremony on the user's device. If successful, the next step will be `DONE`.
421+
422422

423423
```ts
424424
import { type SignInOutput, confirmSignIn } from '@aws-amplify/auth';

0 commit comments

Comments
 (0)