demo · v131

FedCM → SAA flow, step by step

A user signs in to shop.com with a federated identity from idp.com. Later, an embedded idp.com iframe on shop.com needs first-party cookie access. v131 lets the SAA accept the prior FedCM grant as automatic permission — no second prompt. Walk through each step.

step 1

visit shop.com

User opens an e-commerce site that supports federated sign-in.

step 2

FedCM IdP picker

shop.com calls navigator.credentials.get({ identity }). Browser shows the picker.

step 3

token returned

User picks idp.com. Token returned. Browser records: shop.com ↔ idp.com FedCM grant.

step 4

idp.com iframe needs storage

Embedded support widget from idp.com calls document.requestStorageAccess().

step 5

v131: auto-grant

Browser sees the FedCM grant from step 3, auto-resolves the SAA request. No second prompt.

FedCM grant: ? SAA: ?

see also