Open Yekongs opened 1 year ago
The number of them exceeds 3
I assume you know this based on the issue title, but Chrome's limit on the associated subset size is no longer 3, it is now 5. However, you listed 6 sites (plus a service site), so let me address your concern below:
document.requestStorageAccessFor
on behalf of the service site.
document.requestStorageAccess
when embedded in one of those sites, and the request will be automatically granted.document.requestStorageAccess
and potentially prompt the user to ask for permission to use their unpartitioned cookies.There's one other possibility, based on what you wrote:
an enterprise has multiple domain names such as A.com, B.com, C.com, D.com, E.com, F.com,. The number of them exceeds 3, but they all use one within the enterprise,
You've mentioned an enterprise. If you are talking about a company and its employees, and that company uses managed Chrome instances, then the company's enterprise admin can deploy the FirstPartySetsOverrides enterprise policy with a custom set or list of sets. The sets in an enterprise policy are not limited; they can use as many associated sites as they want.
For example, an enterprise has multiple domain names such as A.com, B.com, C.com, D.com, E.com, F.com,. The number of them exceeds 3, but they all use one within the enterprise, such as Z. .com to provide some security services. According to the rules, more than 3 Associates calling requestStorageAccess and requestStorageAccessFor will be automatically rejected. How to solve this problem?