[Gen 2] Add the feedback for custom sign in. #7443
Conversation
| @@ -66,7 +60,7 @@ For more information on adding capabilities to your application, see [Xcode Capa | |||
|
|
|||
| The custom auth flow can be [configured manually](https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-lambda-challenge.html). | |||
|
|
|||
| If you have already configured custom auth, you can use the custom auth flow by changing the `authenticationFlowType` value in your [Amplify configuration](/[platform]/build-a-backend/auth/existing-resources/) to `CUSTOM_AUTH`. | |||
| If you have already configured custom auth, you can use the custom auth flow by changing the `authenticationFlowType` value in your Amplify configuration to `CUSTOM_AUTH`. | |||
There was a problem hiding this comment.
Where can I find this Amplify Configuration? Perhaps an example of setting up the configuration to CUSTOM_AUTH
There was a problem hiding this comment.
It is not moved yet. This will be post GA.
There was a problem hiding this comment.
As per my conversation with @josefaidt, customers should not touch the generated config files and he is removing these in his PR.
| @@ -294,7 +288,7 @@ Confirm sign in succeeded | |||
|
|
|||
| ### Lambda Trigger Setup | |||
|
|
|||
| AWS Amplify now supports creating functions as part of its new backend experience. For more information on the Functions and how to start with them check out [Functions documentation](/[platform]/build-a-backend/functions/). In addition, more information on available triggers can be found in the [Cognito documentation](https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-lambda-challenge.html). | |||
| AWS Amplify now supports creating functions as part of its new backend experience. For more information on the Functions and how to start with them check out [Functions documentation](/[platform]/build-a-backend/functions/). In addition, more information on available triggers can be found in the [Cognito documentation](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html). | |||
|
|
|||
| ### Custom Auth Flow with SRP | |||
There was a problem hiding this comment.
Secure Remote Password
| @@ -946,7 +824,7 @@ user has already signed in and a valid session is active. You must first call | |||
| </Callout> | |||
| ## Confirm sign in with custom challenge | |||
|
|
|||
| Get the custom challenge (`1234` in this case) from the user and pass it to the `confirmSignin()` api. | |||
| Get the custom challenge from the user and pass it to the `confirmSignin()` api. | |||
There was a problem hiding this comment.
How to get it from the user? They will submit the answer to the challenge through a UI?
There was a problem hiding this comment.
Yes and the functions below has a parameter for it.
There was a problem hiding this comment.
Can you update the wording for that i.e. instead of get the ..etc perhaps use something like "Present a UI for the user to submit the answer to the custom challenge and use it ...etc"
src/pages/[platform]/build-a-backend/auth/customize-auth-lifecycle/custom-auth-flows/index.mdx
Show resolved
Hide resolved
Description of changes:
Related GitHub issue #, if available:
Instructions
If this PR should not be merged upon approval for any reason, please submit as a DRAFT
Which product(s) are affected by this PR (if applicable)?
Which platform(s) are affected by this PR (if applicable)?
Please add the product(s)/platform(s) affected to the PR title
Checks
Does this PR conform to the styleguide?
Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.
Are any files being deleted with this PR? If so, have the needed redirects been created?
Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
ref: MDX:
[link](https://docs.amplify.aws/)HTML:
<a href="https://docs.amplify.aws/">link</a>When this PR is ready to merge, please check the box below
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.