Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds a reference to the cookie overflow warning in the dashboard #1776

Merged
merged 2 commits into from
Dec 5, 2024
Merged

Adds a reference to the cookie overflow warning in the dashboard #1776

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2e074da
Adds a reference to the cookie overflow warning in the dashboard
BrandonRomano Dec 5, 2024
4275b73
Update docs/backend-requests/resources/session-tokens.mdx
BrandonRomano Dec 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/backend-requests/resources/session-tokens.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,9 @@ Claims to monitor for size limits:

If you include any of these claims in your token, use caution to ensure the stored data doesn't exceed the size limit.

> [!NOTE]
> If your application encounters this issue, the Clerk Dashboard will display a warning: **"Some users are exceeding cookie size limits"**. To resolve this, update your [custom session token](/docs/backend-requests/making/custom-session-token) or the [JWT template](/docs/backend-requests/making/jwt-templates) that is referenced in the warning.

## Validate session tokens

If you're using the middleware provided by our Clerk SDKs, this is all handled automatically in every request. If you're not using the middleware, you can still use the respective helpers provided by the SDKs to validate the tokens.
Expand Down
Loading