github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-27 01:16:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #1591] [MERGED] docs: added "partitioned: true" for cross-domain (foreign) cookies #3881

New Issue
Closed
opened 2026-03-13 11:19:44 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 11:19:44 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/1591
Author: @nktnet1
Created: 2/27/2025
Status: ✅ Merged
Merged: 2/28/2025
Merged by: @Bekacru

Base: main ← Head: foreign-cookies-partitioned

📝 Commits (1)

  • e98e5b9 docs: added "partitioned: true" for cross-domain (foreign) cookies

📊 Changes

2 files changed (+5 additions, -2 deletions)

View changed files

📝 docs/content/docs/concepts/cookies.mdx (+1 -0)
📝 docs/content/docs/integrations/hono.mdx (+4 -2)

📄 Description

Removes the warning below by using partitioned cookies:

foreign-cookies-warning

raw warnings 
Cookie warnings

Cookie "better-auth.session_token" will soon be rejected because it is foreign and does not have the "Partitioned" attribute.

Cookie "better-auth.session_data" will soon be rejected because it is foreign and does not have the "Partitioned" attribute.

I stumbled upon this issue while deploying my frontend web application and backend server to two different domains - repository below:

  1. Deploy apps/web to one domain
  2. Deploy apps/server to a different domain using the settings 
    advanced: {
  defaultCookieAttributes: {
    sameSite: "none",
    secure: true,
    // partitioned: true                 // comment out to produce warnings
  }
}
  3. Open the browser and register an account - the warnings above can be observed.

Further reading:

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/1591 **Author:** [@nktnet1](https://github.com/nktnet1) **Created:** 2/27/2025 **Status:** ✅ Merged **Merged:** 2/28/2025 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `foreign-cookies-partitioned` --- ### 📝 Commits (1) - [`e98e5b9`](https://github.com/better-auth/better-auth/commit/e98e5b9738e1964f3ffdff46b8c4e4d73496ee11) docs: added "partitioned: true" for cross-domain (foreign) cookies ### 📊 Changes **2 files changed** (+5 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/concepts/cookies.mdx` (+1 -0) 📝 `docs/content/docs/integrations/hono.mdx` (+4 -2) </details> ### 📄 Description Removes the warning below by using partitioned cookies: ![foreign-cookies-warning](https://github.com/user-attachments/assets/043afcd2-5185-46ee-8675-667b24bc53de) <details close> <summary>raw warnings</summary> ``` Cookie warnings Cookie "better-auth.session_token" will soon be rejected because it is foreign and does not have the "Partitioned" attribute. Cookie "better-auth.session_data" will soon be rejected because it is foreign and does not have the "Partitioned" attribute. ``` </details> I stumbled upon this issue while deploying my frontend web application and backend server to two different domains - repository below: - https://github.com/nktnet1/rt-stack 1. Deploy apps/web to one domain 2. Deploy apps/server to a different domain using the settings ```ts advanced: { defaultCookieAttributes: { sameSite: "none", secure: true, // partitioned: true // comment out to produce warnings } } ``` 3. Open the browser and register an account - the warnings above can be observed. Further reading: - https://developers.google.com/privacy-sandbox/cookies/chips-transition - https://developer.mozilla.org/en-US/docs/Web/Privacy/Guides/Privacy_sandbox/Partitioned_cookies - https://github.com/ory/hydra/issues/3703 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-13 11:19:44 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#3881
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?