Skip to content

Commit f54ca4e

Browse files
committed
chore: resolve comments
1 parent 8445d87 commit f54ca4e

File tree

2 files changed

+17
-9
lines changed
  • src/pages
    • [platform]/build-a-backend/server-side-rendering
    • gen1/[platform]/build-a-backend/server-side-rendering/nextjs

2 files changed

+17
-9
lines changed

src/pages/[platform]/build-a-backend/server-side-rendering/index.mdx

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -277,10 +277,14 @@ With the above example, Amplify generates the following API routes:
277277
| `/api/auth/sign-in-callback` | Amazon Cognito Managed Login redirects an end user back to this route after signing in. Amplify exchanges auth tokens and stores them as HttpOnly cookies in the browser cookie store, then redirects the end user back to the route specified by the `redirectOnSignInComplete` parameter. |
278278
| `/api/auth/sign-out-callback` | Amazon Cognito Managed Login redirects an end user back to this route after signing out, Amplify revokes access token and refresh token and removes token cookies from browser cookie store, then redirects the end user back to the route specified by the `redirectOnSignOutComplete` parameter. |
279279

280-
> **Note:** A signing-out call involves multiple steps, including signing out from Amazon Cognito Managed Login, revoking tokens, and removing cookies. If the user closes the browser during the process, the following may occur:
281-
>
282-
> 1. auth token have not been revoked - user remains signed in
283-
> 2. auth token have been revoked but cookies have not been removed - cookies will be removed when the user visits the app again
280+
<Callout info>
281+
282+
**Note:** A signing-out call involves multiple steps, including signing out from Amazon Cognito Managed Login, revoking tokens, and removing cookies. If the user closes the browser during the process, the following may occur:
283+
284+
1. auth token have not been revoked - user remains signed in
285+
2. auth token have been revoked but cookies have not been removed - cookies will be removed when the user visits the app again
286+
287+
</Callout>
284288

285289
#### Step 4 - Provide the redirect URLs to the Auth Resource in Amplify
286290

src/pages/gen1/[platform]/build-a-backend/server-side-rendering/nextjs/index.mdx

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -266,16 +266,20 @@ With the above example, Amplify generates the following API routes:
266266
| `/api/auth/sign-in-callback` | Amazon Cognito Managed Login redirects an end user back to this route after signing in. Amplify exchanges auth tokens and stores them as HttpOnly cookies in the browser cookie store, then redirects the end user back to the route specified by the `redirectOnSignInComplete` parameter. |
267267
| `/api/auth/sign-out-callback` | Amazon Cognito Managed Login redirects an end user back to this route after signing out, Amplify revokes access token and refresh token and removes token cookies from browser cookie store, then redirects the end user back to the route specified by the `redirectOnSignOutComplete` parameter. |
268268

269-
> **Note:** A signing-out call involves multiple steps, including signing out from Amazon Cognito Managed Login, revoking tokens, and removing cookies. If the user closes the browser during the process, the following may occur:
270-
>
271-
> 1. auth token have not been revoked - user remains signed in
272-
> 2. auth token have been revoked but cookies have not been removed - cookies will be removed when the user visits the app again
269+
<Callout info>
270+
271+
**Note:** A signing-out call involves multiple steps, including signing out from Amazon Cognito Managed Login, revoking tokens, and removing cookies. If the user closes the browser during the process, the following may occur:
272+
273+
1. auth token have not been revoked - user remains signed in
274+
2. auth token have been revoked but cookies have not been removed - cookies will be removed when the user visits the app again
275+
276+
</Callout>
273277

274278
#### Step 4 - Provide the redirect URLs to the Auth Resource in Amplify
275279

276280
You can run `amplify add auth` or `amplify update auth` to provide the callback API routes as the redirect URLs. See [Configure the Auth category](/gen1/[platform]/build-a-backend/auth/add-social-provider/#configure-the-auth-category) for more details. With the above example, you can provide the following redirect URLs:
277281

278-
```
282+
```text showLineNumbers={false}
279283
// redirect signin URI:
280284
https://myapp.com/api/auth/sign-in-callback
281285

0 commit comments

Comments
 (0)