From 6216565e7208d573c3079507996b0d1df2f95392 Mon Sep 17 00:00:00 2001 From: rishabhpoddar Date: Sat, 22 Jun 2024 01:48:31 +0530 Subject: [PATCH] fixes typo --- v2/emailpassword/common-customizations/sessions/ssr.mdx | 2 +- v2/passwordless/common-customizations/sessions/ssr.mdx | 2 +- v2/session/common-customizations/sessions/ssr.mdx | 2 +- v2/thirdparty/common-customizations/sessions/ssr.mdx | 2 +- .../common-customizations/sessions/ssr.mdx | 2 +- .../common-customizations/sessions/ssr.mdx | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/v2/emailpassword/common-customizations/sessions/ssr.mdx b/v2/emailpassword/common-customizations/sessions/ssr.mdx index 4b0bd69b9..116901a02 100644 --- a/v2/emailpassword/common-customizations/sessions/ssr.mdx +++ b/v2/emailpassword/common-customizations/sessions/ssr.mdx @@ -32,7 +32,7 @@ Follow the [JWT verification guide](./with-jwt/jwt-verification) to verify the J On the `/refresh-session` page, you want to call the `attemptRefreshingSession` function (from the client side). This function will attempt to refresh the session. If it succeeds, it will return `true`. If it fails, it will return `false`. If it returns `true`, you want to redirect the user back to the page they were on. If it returns `false`, you want to redirect the user to the login page. -## 3) Implementing the refresh session flow (`/refresh-session` pagr) +## 3) Implementing the refresh session flow (`/refresh-session` page) On this path, we want to attempt refreshing the session which can yield: - Success: The frontend will get new access and refresh tokens. Post this, we want to redirect the user to the path mentioned on the `redirectBack` query param. - Failure: This would happen if the session has expired or has been revoked from the backend. Either way, you want to redirect the user to the login page. diff --git a/v2/passwordless/common-customizations/sessions/ssr.mdx b/v2/passwordless/common-customizations/sessions/ssr.mdx index 4b0bd69b9..116901a02 100644 --- a/v2/passwordless/common-customizations/sessions/ssr.mdx +++ b/v2/passwordless/common-customizations/sessions/ssr.mdx @@ -32,7 +32,7 @@ Follow the [JWT verification guide](./with-jwt/jwt-verification) to verify the J On the `/refresh-session` page, you want to call the `attemptRefreshingSession` function (from the client side). This function will attempt to refresh the session. If it succeeds, it will return `true`. If it fails, it will return `false`. If it returns `true`, you want to redirect the user back to the page they were on. If it returns `false`, you want to redirect the user to the login page. -## 3) Implementing the refresh session flow (`/refresh-session` pagr) +## 3) Implementing the refresh session flow (`/refresh-session` page) On this path, we want to attempt refreshing the session which can yield: - Success: The frontend will get new access and refresh tokens. Post this, we want to redirect the user to the path mentioned on the `redirectBack` query param. - Failure: This would happen if the session has expired or has been revoked from the backend. Either way, you want to redirect the user to the login page. diff --git a/v2/session/common-customizations/sessions/ssr.mdx b/v2/session/common-customizations/sessions/ssr.mdx index afab48636..268e74d03 100644 --- a/v2/session/common-customizations/sessions/ssr.mdx +++ b/v2/session/common-customizations/sessions/ssr.mdx @@ -32,7 +32,7 @@ Follow the [JWT verification guide](./with-jwt/jwt-verification) to verify the J On the `/refresh-session` page, you want to call the `attemptRefreshingSession` function (from the client side). This function will attempt to refresh the session. If it succeeds, it will return `true`. If it fails, it will return `false`. If it returns `true`, you want to redirect the user back to the page they were on. If it returns `false`, you want to redirect the user to the login page. -## 3) Implementing the refresh session flow (`/refresh-session` pagr) +## 3) Implementing the refresh session flow (`/refresh-session` page) On this path, we want to attempt refreshing the session which can yield: - Success: The frontend will get new access and refresh tokens. Post this, we want to redirect the user to the path mentioned on the `redirectBack` query param. - Failure: This would happen if the session has expired or has been revoked from the backend. Either way, you want to redirect the user to the login page. diff --git a/v2/thirdparty/common-customizations/sessions/ssr.mdx b/v2/thirdparty/common-customizations/sessions/ssr.mdx index 4b0bd69b9..116901a02 100644 --- a/v2/thirdparty/common-customizations/sessions/ssr.mdx +++ b/v2/thirdparty/common-customizations/sessions/ssr.mdx @@ -32,7 +32,7 @@ Follow the [JWT verification guide](./with-jwt/jwt-verification) to verify the J On the `/refresh-session` page, you want to call the `attemptRefreshingSession` function (from the client side). This function will attempt to refresh the session. If it succeeds, it will return `true`. If it fails, it will return `false`. If it returns `true`, you want to redirect the user back to the page they were on. If it returns `false`, you want to redirect the user to the login page. -## 3) Implementing the refresh session flow (`/refresh-session` pagr) +## 3) Implementing the refresh session flow (`/refresh-session` page) On this path, we want to attempt refreshing the session which can yield: - Success: The frontend will get new access and refresh tokens. Post this, we want to redirect the user to the path mentioned on the `redirectBack` query param. - Failure: This would happen if the session has expired or has been revoked from the backend. Either way, you want to redirect the user to the login page. diff --git a/v2/thirdpartyemailpassword/common-customizations/sessions/ssr.mdx b/v2/thirdpartyemailpassword/common-customizations/sessions/ssr.mdx index 4b0bd69b9..116901a02 100644 --- a/v2/thirdpartyemailpassword/common-customizations/sessions/ssr.mdx +++ b/v2/thirdpartyemailpassword/common-customizations/sessions/ssr.mdx @@ -32,7 +32,7 @@ Follow the [JWT verification guide](./with-jwt/jwt-verification) to verify the J On the `/refresh-session` page, you want to call the `attemptRefreshingSession` function (from the client side). This function will attempt to refresh the session. If it succeeds, it will return `true`. If it fails, it will return `false`. If it returns `true`, you want to redirect the user back to the page they were on. If it returns `false`, you want to redirect the user to the login page. -## 3) Implementing the refresh session flow (`/refresh-session` pagr) +## 3) Implementing the refresh session flow (`/refresh-session` page) On this path, we want to attempt refreshing the session which can yield: - Success: The frontend will get new access and refresh tokens. Post this, we want to redirect the user to the path mentioned on the `redirectBack` query param. - Failure: This would happen if the session has expired or has been revoked from the backend. Either way, you want to redirect the user to the login page. diff --git a/v2/thirdpartypasswordless/common-customizations/sessions/ssr.mdx b/v2/thirdpartypasswordless/common-customizations/sessions/ssr.mdx index 4b0bd69b9..116901a02 100644 --- a/v2/thirdpartypasswordless/common-customizations/sessions/ssr.mdx +++ b/v2/thirdpartypasswordless/common-customizations/sessions/ssr.mdx @@ -32,7 +32,7 @@ Follow the [JWT verification guide](./with-jwt/jwt-verification) to verify the J On the `/refresh-session` page, you want to call the `attemptRefreshingSession` function (from the client side). This function will attempt to refresh the session. If it succeeds, it will return `true`. If it fails, it will return `false`. If it returns `true`, you want to redirect the user back to the page they were on. If it returns `false`, you want to redirect the user to the login page. -## 3) Implementing the refresh session flow (`/refresh-session` pagr) +## 3) Implementing the refresh session flow (`/refresh-session` page) On this path, we want to attempt refreshing the session which can yield: - Success: The frontend will get new access and refresh tokens. Post this, we want to redirect the user to the path mentioned on the `redirectBack` query param. - Failure: This would happen if the session has expired or has been revoked from the backend. Either way, you want to redirect the user to the login page.