You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `signIn` API response will include a `nextStep` property, which can be used to determine if further action is required. It may return the following next steps:
-`CONFIRM_SIGN_IN_WITH_NEW_PASSWORD_REQUIRED` - The user was created with a temporary password and must set a new one. Complete the process with `confirmSignIn`.
258
+
-`CONFIRM_SIGN_IN_WITH_CUSTOM_CHALLENGE` - The sign-in must be confirmed with a custom challenge response. Complete the process with `confirmSignIn`.
259
+
-`CONFIRM_SIGN_IN_WITH_TOTP_CODE` - The sign-in must be confirmed with a TOTP code from the user. Complete the process with `confirmSignIn`.
260
+
-`CONTINUE_SIGN_IN_WITH_TOTP_SETUP` - The TOTP setup process must be continued. Complete the process with `confirmSignIn`.
261
+
-`CONFIRM_SIGN_IN_WITH_SMS_CODE` - The sign-in must be confirmed with a SMS code from the user. Complete the process with `confirmSignIn`.
262
+
-`CONTINUE_SIGN_IN_WITH_MFA_SELECTION` - The user must select their mode of MFA verification before signing in. Complete the process with `confirmSignIn`.
263
+
-`RESET_PASSWORD` - The user must reset their password via `resetPassword`.
264
+
-`CONFIRM_SIGN_UP` - The user hasn't completed the sign-up flow fully and must be confirmed via `confirmSignUp`.
265
+
-`DONE` - The sign in process has been completed.
275
266
</InlineFilter>
276
267
277
-
<InlineFilterfilters={['swift', 'flutter']}>
278
-
-`confirmSignInWithNewPassword` - The user was created with a temporary
279
-
password and must set a new one. Complete the process with `confirmSignIn`. -
280
-
`confirmSignInWithCustomChallenge` - The sign-in must be confirmed with a
281
-
custom challenge response. Complete the process with `confirmSignIn`. -
282
-
`confirmSignInWithTOTPCode` - The sign-in must be confirmed with a TOTP code
283
-
from the user. Complete the process with `confirmSignIn`. -
284
-
`continueSignInWithTOTPSetup` - The TOTP setup process must be continued.
285
-
Complete the process with `confirmSignIn`. - `confirmSignInWithSMSMFACode` -
286
-
The sign-in must be confirmed with a SMS code from the user. Complete the
287
-
process with `confirmSignIn`. - `continueSignInWithMFASelection` - The user
288
-
must select their mode of MFA verification before signing in. Complete the
289
-
process with `confirmSignIn`. - `resetPassword` - The user must reset their
290
-
password via `resetPassword`. - `confirmSignUp` - The user hasn't completed
291
-
the sign-up flow fully and must be confirmed via `confirmSignUp`. - `done` -
292
-
The sign in process has been completed.
268
+
<InlineFilterfilters={["swift", "flutter"]}>
269
+
-`confirmSignInWithNewPassword` - The user was created with a temporary password and must set a new one. Complete the process with `confirmSignIn`.
270
+
-`confirmSignInWithCustomChallenge` - The sign-in must be confirmed with a custom challenge response. Complete the process with `confirmSignIn`.
271
+
-`confirmSignInWithTOTPCode` - The sign-in must be confirmed with a TOTP code from the user. Complete the process with `confirmSignIn`.
272
+
-`continueSignInWithTOTPSetup` - The TOTP setup process must be continued. Complete the process with `confirmSignIn`.
273
+
-`confirmSignInWithSMSMFACode` - The sign-in must be confirmed with a SMS code from the user. Complete the process with `confirmSignIn`.
274
+
-`continueSignInWithMFASelection` - The user must select their mode of MFA verification before signing in. Complete the process with `confirmSignIn`.
275
+
-`resetPassword` - The user must reset their password via `resetPassword`.
276
+
-`confirmSignUp` - The user hasn't completed the sign-up flow fully and must be confirmed via `confirmSignUp`.
277
+
-`done` - The sign in process has been completed.
293
278
</InlineFilter>
294
279
295
280
For more information on handling the TOTP and MFA steps that may be returned, see [multi-factor authentication](/[platform]/build-a-backend/auth/concepts/multi-factor-authentication/).
@@ -299,22 +284,20 @@ For more information on handling the TOTP and MFA steps that may be returned, se
`signIn` API even allows you to continue confirm sign-in process after a redirection to a different location requiring a full browser reload, such as redirecting from a Login Page to a Confirm MFA Code Page in a Multi-Page Application during the sign-in process.
When multi-factor authentication (MFA) is **required** with SMS in your backend auth resource, you will need to pass the phone number during sign-up API call. If you are using the `email` or `username` as the primary sign-in mechanism, you will need to pass the `phone_number` attribute as a user attribute. This will change depending on if you enable SMS, TOTP, or both. Visit the [multi-factor authentication documentation](/[platform]/build-a-backend/auth/concepts/multi-factor-authentication/) to learn more about enabling MFA on your backend auth resource.
You will then confirm sign-up, sign in, and receive a `nextStep` in the sign-in result of type `CONFIRM_SIGN_IN_WITH_SMS_MFA_CODE`. A confirmation code will also be texted to the phone number provided above. Pass the code you received to the `confirmSignIn` API:
587
555
</InlineFilter>
588
556
589
-
<InlineFilterfilters={['swift']}>
590
-
You will then confirm sign-up, sign in, and receive a `nextStep` in the
591
-
sign-in result of type `confirmSignInWithSMSMFACode`. A confirmation code will
592
-
also be texted to the phone number provided above. Pass the code you received
593
-
to the `confirmSignIn` API:
557
+
<InlineFilterfilters={["swift"]}>
558
+
You will then confirm sign-up, sign in, and receive a `nextStep` in the sign-in result of type `confirmSignInWithSMSMFACode`. A confirmation code will also be texted to the phone number provided above. Pass the code you received to the `confirmSignIn` API:
Alternatively if you have configured OIDC or SAML-based identity providers in your auth resource, you can specify a "custom" provider in `signInWithRedirect`:
Sign-in with web UI requires the Amplify plugin to show up the sign-in UI inside a webview. After the sign-in process is complete it will redirect back to your app. You have to enable this in your app's `Info.plist`. Right click Info.plist and then choose Open As > Source Code. Add the following entry in the URL scheme:
895
+
Sign-in with web UI requires the Amplify plugin to show up the sign-in UI inside a webview. After the sign-in process is complete it will redirect back to your app.
896
+
You have to enable this in your app's `Info.plist`. Right click Info.plist and then choose Open As > Source Code. Add the following entry in the URL scheme:
0 commit comments