From c79854ad0ba151e2fda07ff3ce5bad0a4bc0af49 Mon Sep 17 00:00:00 2001 From: Michiel de Jong Date: Mon, 25 Nov 2024 11:26:03 +0100 Subject: [PATCH 1/4] update demo instructions This functionality has now shipped in regular Chrome and is no longer under a flag. I also edited the demo steps a bit so they seemed more logical to me. --- README.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 1d476c5..7e876e4 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ npm run build npm run start ``` -First you need chrome canary / dev build version > 129 with the `FedCM Authz`, `FedCmMultiIdp` and `FedCM with IdP Registration support` flags enabled in `chrome://flags/` +First you need to use a browser that supports FedCM, such as Chrome (version tested: 131). No special config flags are necessary. ## On localhost @@ -17,15 +17,16 @@ First you need chrome canary / dev build version > 129 with the `FedCM Authz`, - open a private window - first go to [http://localhost:3000/.account/](http://localhost:3000/.account/) , click `register IdP to FedCM` and log in with the account created in the previous step - then go to the client at [http://localhost:6080](http://localhost:6080) - - note: if you try to fetch your profile at `http://localhost:3000//profile/` on step 3. You will get an error, as you need to be logged to access this resource. - - Trigger the Dynamic Client Registration on 1) - - Click the fedcm login button on 2) - - Now try to fetch your profile on 3) again, you should receive the resource without an error. + - under section 3) of the page, edit the textbox so that it has your profile folder instead of 'http://localhost:3000/a/profile/' + - confirm that 'Fetch resource' results in a 401 error. + - under section 2) of the page, click the fedcm login button. It will offer to log you in as 'John Doe', but with your WebID from the previous step. + - confirm that your WebID and an access token appear. + - click 'Fetch resource' again. It should display an `ldp:Container` description ## hosted if the client and CSS don't have the same domain or subdomain, the current CSS instance in `./packages/fedcm-component/` won't work because of the `SameSite=None` cookie policiy of FedCM. -Please refere to [this repo](https://github.com/thhck/fedcm-css-exp) instead +Please refer to [this repo](https://github.com/thhck/fedcm-css-exp) instead # demo From ee3ad7f43259313934c7cb48784c80869af0ca74 Mon Sep 17 00:00:00 2001 From: Michiel de Jong Date: Mon, 25 Nov 2024 11:27:13 +0100 Subject: [PATCH 2/4] clarify `http://localhost:3000//profile/` --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7e876e4..8b06c89 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,7 @@ First you need to use a browser that supports FedCM, such as Chrome (version tes - open a private window - first go to [http://localhost:3000/.account/](http://localhost:3000/.account/) , click `register IdP to FedCM` and log in with the account created in the previous step - then go to the client at [http://localhost:6080](http://localhost:6080) - - under section 3) of the page, edit the textbox so that it has your profile folder instead of 'http://localhost:3000/a/profile/' + - under section 3) of the page, edit the textbox so that it has your profile folder `http://localhost:3000//profile/` instead of `http://localhost:3000/a/profile/` - confirm that 'Fetch resource' results in a 401 error. - under section 2) of the page, click the fedcm login button. It will offer to log you in as 'John Doe', but with your WebID from the previous step. - confirm that your WebID and an access token appear. From 8fbe9b8a298cb17244ade06acd20f905dc1bd75b Mon Sep 17 00:00:00 2001 From: Michiel de Jong Date: Mon, 25 Nov 2024 11:30:12 +0100 Subject: [PATCH 3/4] make text box readable --- packages/client/public/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/client/public/index.html b/packages/client/public/index.html index 5933efd..20ecac8 100644 --- a/packages/client/public/index.html +++ b/packages/client/public/index.html @@ -22,7 +22,7 @@

2. Login

3. Fetch a protected resource

- +

Response

From 6e6328e54bcb74eb7899c974da96303fc5eb832a Mon Sep 17 00:00:00 2001 From: Michiel de Jong Date: Mon, 25 Nov 2024 16:43:27 +0100 Subject: [PATCH 4/4] updated instructions re chrome://flags Following info from https://github.com/w3c-fedid/idp-registration/issues/2#issuecomment-2336490996 --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8b06c89..bf6a021 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,9 @@ npm run build npm run start ``` -First you need to use a browser that supports FedCM, such as Chrome (version tested: 131). No special config flags are necessary. +First you need to use a browser that supports FedCM, such as: +* use Chrome >= 128, go to chrome://flags and enter "fedcm" to filter the flags +* Enable "FedCM with IdP Registration support" and "FedCmMultiIdp" ## On localhost