Make sure you use a Chromium-based browser (version > 126 for Chromium) with the FedCM flag enabled
- Go to chrome://flags and enter "fedcm" to filter the flags
- Enable "FedCM with IdP Registration support" and "FedCmMultiIdp"
Make sure you use a Chromium-based browser (version > 126 for Chromium) with the FedCM flag enabled
FedCM requires you to have a logged-in session from an IdP, in our case, a Solid server based on CSS. If your IdP is FedCM-compatible, you should only log in, and everything should be handled by the server.
Currently, the only FedCM-compatible Solid server available is this demo CSS instance.
(The compatibility is provided by this add-on
and by changing the cookie policy to SameSite=None
, which also makes the server vulnerable,
so it should be used for testing purposes only. It should be resolved in the future. See #587).
First, you need to create an account here,
or just log in with the demo account:
alice@example.org
alice
When you log in to CSS don't forget to click the "Register IdP" button before logging in
You can log in here Now, if you try to fetch the resource below, you should receive an error:
This is because you are trying to access a container (/profile
) that is private by
default.
So let's log in using FedCM to fetch the resource.
We are now logged in. As you can see, FedCM has automatically found the Solid server we were logged into.
We also didn't have a redirection to our Solid server, nor a consent screen... pretty good UX! Try to fetch the resource again to confirm you're logged in.