-
Notifications
You must be signed in to change notification settings - Fork 32
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.
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
Embedded applications that use multiple subdomains #39
Comments
Hello and thanks for your interest in CHIPS. We understand that making partitioned cookies hostname bound is a paradigm shift from domain-bound unpartitioned cross-site cookies. Here are some solutions that sites can use to migrate to hostname-bound cross-site cookies:
If these solutions do not work for your use case, we are interested in hearing your feedback as to why so that we can work together on new solutions. |
Closing this now that #43 is also closed. CHIPS no longer requires cookies to not be set with Domain. |
@DCtheTall I am aware that the use case in this issue has not been resolved. |
It was my lack of knowledge. I was not aware of the specification changes. |
How would this work for an application embedded in an iframe that uses multiple subdomains in a 3rd party context?
For example, an org owns:
api.example.com
account.example.com
app1.example.com
app2.example.com
There is an authentication token set in a cookie by api.example.com meant to available to all example.com sub-domains. The sites listed are the same party but also need partitioned and keyed to a top level site.
The text was updated successfully, but these errors were encountered: