Merge pull request #656 from supertokens/doc-updates

Adds missing email verification snippet
supertokens · May 10, 2023 · 35d6b62 · 35d6b62
2 parents c6b751a + 6604a1c
commit 35d6b62
Show file tree

Hide file tree

Showing 10 changed files with 60 additions and 0 deletions.
diff --git a/v2/emailpassword/common-customizations/email-verification/protecting-routes.mdx b/v2/emailpassword/common-customizations/email-verification/protecting-routes.mdx
@@ -1403,6 +1403,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </AppInfoForm>
 
 </TabItem>

diff --git a/v2/emailpassword/custom-ui/enable-email-verification.mdx b/v2/emailpassword/custom-ui/enable-email-verification.mdx
@@ -818,6 +818,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </TabItem>
 </FrontendCustomUITabs>
 

diff --git a/v2/passwordless/common-customizations/email-verification/protecting-routes.mdx b/v2/passwordless/common-customizations/email-verification/protecting-routes.mdx
@@ -1403,6 +1403,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </AppInfoForm>
 
 </TabItem>

diff --git a/v2/passwordless/custom-ui/enable-email-verification.mdx b/v2/passwordless/custom-ui/enable-email-verification.mdx
@@ -822,6 +822,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </TabItem>
 </FrontendCustomUITabs>
 

diff --git a/v2/thirdparty/common-customizations/email-verification/protecting-routes.mdx b/v2/thirdparty/common-customizations/email-verification/protecting-routes.mdx
@@ -1403,6 +1403,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </AppInfoForm>
 
 </TabItem>

diff --git a/v2/thirdparty/custom-ui/enable-email-verification.mdx b/v2/thirdparty/custom-ui/enable-email-verification.mdx
@@ -822,6 +822,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </TabItem>
 </FrontendCustomUITabs>
 

diff --git a/...rtyemailpassword/common-customizations/email-verification/protecting-routes.mdx b/...rtyemailpassword/common-customizations/email-verification/protecting-routes.mdx
@@ -1404,6 +1404,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </AppInfoForm>
 
 </TabItem>

diff --git a/v2/thirdpartyemailpassword/custom-ui/enable-email-verification.mdx b/v2/thirdpartyemailpassword/custom-ui/enable-email-verification.mdx
@@ -822,6 +822,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </TabItem>
 </FrontendCustomUITabs>
 

diff --git a/...artypasswordless/common-customizations/email-verification/protecting-routes.mdx b/...artypasswordless/common-customizations/email-verification/protecting-routes.mdx
@@ -1403,6 +1403,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </AppInfoForm>
 
 </TabItem>

diff --git a/v2/thirdpartypasswordless/custom-ui/enable-email-verification.mdx b/v2/thirdpartypasswordless/custom-ui/enable-email-verification.mdx
@@ -823,6 +823,12 @@ Future<void> checkIfEmailIsVerified() async {
 
 </FrontendMobileSubTabs>
 
+<details><summary>Handling 403 responses on the frontend</summary>
+
+If your frontend queries a protected API on your backend and it fails with a 403, you can check the value of the `st-ev` claim in the access token payload. If it is set to false you can send the verification email
+
+</details>
+
 </TabItem>
 </FrontendCustomUITabs>