From 5425741eabf83285ede122c321123abff99f43e2 Mon Sep 17 00:00:00 2001 From: rishabhpoddar Date: Wed, 1 May 2024 00:00:36 +0530 Subject: [PATCH] small copy change --- .../sessions/jwt-signing-key-rotation.mdx | 20 ++----------------- .../sessions/with-jwt/jwt-verification.mdx | 20 ++----------------- .../sessions/jwt-signing-key-rotation.mdx | 20 ++----------------- .../sessions/with-jwt/jwt-verification.mdx | 20 ++----------------- .../sessions/jwt-signing-key-rotation.mdx | 20 ++----------------- .../sessions/with-jwt/jwt-verification.mdx | 20 ++----------------- .../sessions/jwt-signing-key-rotation.mdx | 20 ++----------------- .../sessions/with-jwt/jwt-verification.mdx | 20 ++----------------- .../sessions/jwt-signing-key-rotation.mdx | 20 ++----------------- .../sessions/with-jwt/jwt-verification.mdx | 20 ++----------------- .../sessions/jwt-signing-key-rotation.mdx | 20 ++----------------- .../sessions/with-jwt/jwt-verification.mdx | 20 ++----------------- 12 files changed, 24 insertions(+), 216 deletions(-) diff --git a/v2/emailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx b/v2/emailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx index b4ab73477..168857aed 100644 --- a/v2/emailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx +++ b/v2/emailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx @@ -121,15 +121,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -153,15 +145,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/emailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx b/v2/emailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx index d1f0e905a..1debf9c2f 100644 --- a/v2/emailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx +++ b/v2/emailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx @@ -201,15 +201,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -233,15 +225,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/passwordless/common-customizations/sessions/jwt-signing-key-rotation.mdx b/v2/passwordless/common-customizations/sessions/jwt-signing-key-rotation.mdx index dd357fd96..140f6943d 100644 --- a/v2/passwordless/common-customizations/sessions/jwt-signing-key-rotation.mdx +++ b/v2/passwordless/common-customizations/sessions/jwt-signing-key-rotation.mdx @@ -121,15 +121,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -153,15 +145,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/passwordless/common-customizations/sessions/with-jwt/jwt-verification.mdx b/v2/passwordless/common-customizations/sessions/with-jwt/jwt-verification.mdx index d1f0e905a..1debf9c2f 100644 --- a/v2/passwordless/common-customizations/sessions/with-jwt/jwt-verification.mdx +++ b/v2/passwordless/common-customizations/sessions/with-jwt/jwt-verification.mdx @@ -201,15 +201,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -233,15 +225,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/session/common-customizations/sessions/jwt-signing-key-rotation.mdx b/v2/session/common-customizations/sessions/jwt-signing-key-rotation.mdx index 273c8e6ca..fd3003975 100644 --- a/v2/session/common-customizations/sessions/jwt-signing-key-rotation.mdx +++ b/v2/session/common-customizations/sessions/jwt-signing-key-rotation.mdx @@ -121,15 +121,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -153,15 +145,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/session/common-customizations/sessions/with-jwt/jwt-verification.mdx b/v2/session/common-customizations/sessions/with-jwt/jwt-verification.mdx index e3916b7a5..79543204c 100644 --- a/v2/session/common-customizations/sessions/with-jwt/jwt-verification.mdx +++ b/v2/session/common-customizations/sessions/with-jwt/jwt-verification.mdx @@ -201,15 +201,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -233,15 +225,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/thirdparty/common-customizations/sessions/jwt-signing-key-rotation.mdx b/v2/thirdparty/common-customizations/sessions/jwt-signing-key-rotation.mdx index b4ab73477..168857aed 100644 --- a/v2/thirdparty/common-customizations/sessions/jwt-signing-key-rotation.mdx +++ b/v2/thirdparty/common-customizations/sessions/jwt-signing-key-rotation.mdx @@ -121,15 +121,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -153,15 +145,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/thirdparty/common-customizations/sessions/with-jwt/jwt-verification.mdx b/v2/thirdparty/common-customizations/sessions/with-jwt/jwt-verification.mdx index d1f0e905a..1debf9c2f 100644 --- a/v2/thirdparty/common-customizations/sessions/with-jwt/jwt-verification.mdx +++ b/v2/thirdparty/common-customizations/sessions/with-jwt/jwt-verification.mdx @@ -201,15 +201,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -233,15 +225,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/thirdpartyemailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx b/v2/thirdpartyemailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx index b4ab73477..168857aed 100644 --- a/v2/thirdpartyemailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx +++ b/v2/thirdpartyemailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx @@ -121,15 +121,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -153,15 +145,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/thirdpartyemailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx b/v2/thirdpartyemailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx index d1f0e905a..1debf9c2f 100644 --- a/v2/thirdpartyemailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx +++ b/v2/thirdpartyemailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx @@ -201,15 +201,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -233,15 +225,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/thirdpartypasswordless/common-customizations/sessions/jwt-signing-key-rotation.mdx b/v2/thirdpartypasswordless/common-customizations/sessions/jwt-signing-key-rotation.mdx index dd357fd96..140f6943d 100644 --- a/v2/thirdpartypasswordless/common-customizations/sessions/jwt-signing-key-rotation.mdx +++ b/v2/thirdpartypasswordless/common-customizations/sessions/jwt-signing-key-rotation.mdx @@ -121,15 +121,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -153,15 +145,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: diff --git a/v2/thirdpartypasswordless/common-customizations/sessions/with-jwt/jwt-verification.mdx b/v2/thirdpartypasswordless/common-customizations/sessions/with-jwt/jwt-verification.mdx index d1f0e905a..1debf9c2f 100644 --- a/v2/thirdpartypasswordless/common-customizations/sessions/with-jwt/jwt-verification.mdx +++ b/v2/thirdpartypasswordless/common-customizations/sessions/with-jwt/jwt-verification.mdx @@ -201,15 +201,7 @@ func main() { ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. ::: @@ -233,15 +225,7 @@ init( ``` :::caution -Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop): - -If `useDynamicAccessTokenSigningKey` is false: -- `UPDATE session_info SET use_static_key = true;` - -Else if `useDynamicAccessTokenSigningKey` is true: -- `UPDATE session_info SET use_static_key = false;` - -If you are using the managed core, you can send an email to us about this, and we will run the query for you. +Updating this value will cause a spike in the session refresh API, as and when users visit your application. :::