Skip to content

Commit

Permalink
small copy change
Browse files Browse the repository at this point in the history
  • Loading branch information
@rishabhpoddar
rishabhpoddar committed Apr 30, 2024
1 parent 5776b39 commit 5425741
Show file tree
Hide file tree
Showing 12 changed files with 24 additions and 216 deletions.
20 changes: 2 additions & 18 deletions v2/emailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions v2/emailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions v2/passwordless/common-customizations/sessions/jwt-signing-key-rotation.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions v2/passwordless/common-customizations/sessions/with-jwt/jwt-verification.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions v2/session/common-customizations/sessions/jwt-signing-key-rotation.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions v2/session/common-customizations/sessions/with-jwt/jwt-verification.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions v2/thirdparty/common-customizations/sessions/jwt-signing-key-rotation.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions v2/thirdparty/common-customizations/sessions/with-jwt/jwt-verification.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions ...dpartyemailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions ...partyemailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
20 changes: 2 additions & 18 deletions ...rdpartypasswordless/common-customizations/sessions/jwt-signing-key-rotation.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::

</TabItem>
Expand All @@ -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.
:::


Expand Down
Loading

0 comments on commit 5425741

Please sign in to comment.