explainers-by-googlers/storage-access-for-fedcm

This proposal reconciles the FedCM and Storage Access APIs by making a prior FedCM grant a valid reason to automatically approve a storage access request.

storage-access-for-fedcm's Issues

Find a way to make top-level storage access work

As @bvandersloot-mozilla rightfully pointed out in today's Privacy CG call, concepts like rSAFor and the Storage Access Headers wouldn't be compatible with this proposal's idea of scoping access using the identity-credentials-get policy.

I suspect the only way we can make this work would be if the RP sets a header-based permissions policy and thus opts all resources of the IdP into receiving storage access. Based on my understanding this mostly works because the only feedback about top-level Fetch use cases for Storage Access Headers comes from developers that control both the RP and IdP in some way.

Incorporate Prevent Silent Access into this proposal

As @bvandersloot points out in fedidcg/CrossSiteCookieAccessCredential#8, we should not auto-grant storage access if prevent silent access is activated for the top-level (RP) origin.

SEO

GÜLER AĞIR MAKİNALI SİLAH ÜRETİM TİCARET SANAYİ TEXAS AŞ