Skip to content

Commit 69f91a9

Browse files
authored
Update switch-auth.mdx (#5455)
Updated "back-end" to "backend" Updated "Setup" to "Set up" ("set up" is two words when used as a compound verb)
1 parent 25a348e commit 69f91a9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/fragments/lib/auth/js/switch-auth.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ For client side authentication there are three different flows:
33

44
1. `USER_SRP_AUTH`: The `USER_SRP_AUTH` flow uses the [SRP protocol (Secure Remote Password)](https://en.wikipedia.org/wiki/Secure_Remote_Password_protocol) where the password never leaves the client and is unknown to the server. This is the recommended flow and is used by default.
55

6-
2. `USER_PASSWORD_AUTH`: The `USER_PASSWORD_AUTH` flow will send user credentials unencrypted to the back-end. If you want to migrate users to Cognito using the "Migration" trigger and avoid forcing users to reset their passwords, you will need to use this authentication type because the Lambda function invoked by the trigger needs to verify the supplied credentials.
6+
2. `USER_PASSWORD_AUTH`: The `USER_PASSWORD_AUTH` flow will send user credentials unencrypted to the backend. If you want to migrate users to Cognito using the "Migration" trigger and avoid forcing users to reset their passwords, you will need to use this authentication type because the Lambda function invoked by the trigger needs to verify the supplied credentials.
77

88
3. `CUSTOM_AUTH`: The `CUSTOM_AUTH` flow is used to allow for a series of challenge and response cycles that can be customized to meet different requirements.
99

@@ -23,7 +23,7 @@ Auth.configure({
2323

2424
A use case for the `USER_PASSWORD_AUTH` authentication flow is migrating users into Amazon Cognito
2525

26-
### Setup auth backend
26+
### Set up auth backend
2727

2828
In order to use the authentication flow `USER_PASSWORD_AUTH`, your Cognito app client has to be configured to allow it. In the AWS Console, this is done by ticking the checkbox at General settings > App clients > Show Details (for the affected client) > Enable username-password (non-SRP) flow. If you're using the AWS CLI or CloudFormation, update your app client by adding `USER_PASSWORD_AUTH` to the list of "Explicit Auth Flows".
2929

@@ -130,4 +130,4 @@ export const handler = async (event, context) => {
130130

131131
return event;
132132
};
133-
```
133+
```

0 commit comments

Comments
 (0)