Federated Identity Working Group - Activity in 2025
No matches.
TR publications
-
4 documents published.
-
Digital Credentials published 4 times as a Working Draft. History of Digital Credentials
-
Past meetings
Participants
-
1 participant joined.
-
Luke Dary (IBM Corporation) joined.
-
-
1 participant left.
-
Brent Zundel (Tradeverifyd) left.
-
GitHub
w3c-fedid/FedCM
-
3 issues opened.
-
Leatch w3c-fedid/FedCM#798, by @robertstirratisgay-tech.
-
Stolen data cookie in private browser w3c-fedid/FedCM#797, by @robertstirratisgay-tech.
-
788750 w3c-fedid/FedCM#796, by @juanalbertoplatagutierrez66-web.
-
-
3 issues closed.
-
Leatch w3c-fedid/FedCM#798.
-
Stolen data cookie in private browser w3c-fedid/FedCM#797.
-
788750 w3c-fedid/FedCM#796.
-
-
5 issues received 13 new comments.
-
Augment autofill with a `conditional` get w3c-fedid/FedCM#694 (6 comments by @samuelgoto, @timcappalli, @wseltzer, @yi-gu)
-
w3c-fedid/digital-credentials
-
8 issues opened.
-
Define DC API behavior in Private Browsing Mode w3c-fedid/digital-credentials#416, by @mohamedamir.
-
Terms: Use "credential manager" in technical references w3c-fedid/digital-credentials#414, by @timcappalli.
-
Terms: Add "wallet" and "digital wallet" with alias to credential manager w3c-fedid/digital-credentials#413, by @timcappalli.
-
Terms: link "credential manager" to CredMan w3c-fedid/digital-credentials#412, by @timcappalli.
-
Terms: add issuer service and verifier service w3c-fedid/digital-credentials#411, by @timcappalli.
-
Rename Model to Terminology w3c-fedid/digital-credentials#410, by @timcappalli.
-
Terminology Updates and Additions w3c-fedid/digital-credentials#409, by @timcappalli.
-
Run cspell on GitHub server as a pre-commit hook w3c-fedid/digital-credentials#404, by @marcoscaceres.
-
-
4 issues closed.
-
Horizontal Review - Architecture w3c-fedid/digital-credentials#230.
-
explainer: fix "do nothing" link w3c-fedid/digital-credentials#363.
-
Run cspell on GitHub server as a pre-commit hook w3c-fedid/digital-credentials#404.
-
Add a terminology section w3c-fedid/digital-credentials#352.
-
-
12 issues received 25 new comments.
-
Run cspell on GitHub server as a pre-commit hook w3c-fedid/digital-credentials#404 (5 comments by @marcoscaceres, @TallTed, @timcappalli)
-
The digital credential definition should include "verifiable" aspect w3c-fedid/digital-credentials#198 (3 comments by @marcoscaceres, @TallTed)
-
Add error for when the API is supported, but the platform doesn't support it w3c-fedid/digital-credentials#359 (3 comments by @marcoscaceres, @mohamedamir, @timcappalli)
-
Add guidance to verifiers/issuers and clients/client platforms on cross-origin usage w3c-fedid/digital-credentials#332 (2 comments by @marcoscaceres, @mohamedamir)
-
Define DC API behavior in Private Browsing Mode w3c-fedid/digital-credentials#416 (2 comments by @marcoscaceres, @mohamedamir)
-
examples or explainability about what might be in the `data` parameters w3c-fedid/digital-credentials#315 (1 comment by @marcoscaceres)
-
Should response encryption be required w3c-fedid/digital-credentials#109 (1 comment by @simoneonofri)
-
Terms: Add "wallet" and "digital wallet" with alias to credential manager w3c-fedid/digital-credentials#413 (1 comment by @marcoscaceres)
-
-
11 pull requests opened.
-
Adds missing contributors w3c-fedid/digital-credentials#422, by @timcappalli.
-
Define "complete credential request with error" w3c-fedid/digital-credentials#421, by @marcoscaceres.
-
Define "prepare credential requests" algorithm w3c-fedid/digital-credentials#420, by @marcoscaceres.
-
Define "present credential requests" algorithm. w3c-fedid/digital-credentials#419, by @marcoscaceres.
-
Fixup algorithms in credential creation and request steps. w3c-fedid/digital-credentials#418, by @marcoscaceres.
-
Introduce "active promise" concept for request coordinator. w3c-fedid/digital-credentials#417, by @marcoscaceres.
-
chore: Explainer - tweak "do nothing" text w3c-fedid/digital-credentials#415, by @timcappalli.
-
chore: add agent review instructions w3c-fedid/digital-credentials#407, by @marcoscaceres.
-
Typos w3c-fedid/digital-credentials#403, by @timcappalli.
-
chore: Adds cspell config w3c-fedid/digital-credentials#402, by @timcappalli.
-
Change from Registry to Protocols w3c-fedid/digital-credentials#401, by @timcappalli.
-
-
5 pull requests merged.
-
chore: add agent review instructions w3c-fedid/digital-credentials#407.
-
Adds missing contributors w3c-fedid/digital-credentials#422.
-
chore: Explainer - tweak "do nothing" text w3c-fedid/digital-credentials#415.
-
chore: Adds cspell config w3c-fedid/digital-credentials#402.
-
Typos w3c-fedid/digital-credentials#403.
-
-
4 pull requests closed.
-
Get steps w3c-fedid/digital-credentials#372.
-
Define Digital Wallet w3c-fedid/digital-credentials#386.
-
Remove registry w3c-fedid/digital-credentials#376.
-
Add terminology section, merge in Model w3c-fedid/digital-credentials#387.
-
-
16 pull requests received 58 new comments.
-
Change from Registry to Protocols w3c-fedid/digital-credentials#401 (17 comments by @marcoscaceres, @RByers, @TallTed, @timcappalli)
-
chore: add agent review instructions w3c-fedid/digital-credentials#407 (6 comments by @marcoscaceres, @TallTed)
-
chore: Adds cspell config w3c-fedid/digital-credentials#402 (5 comments by @marcoscaceres, @timcappalli)
-
Fallback to Cred Man when the API is not supported w3c-fedid/digital-credentials#395 (4 comments by @marcoscaceres, @mohamedamir, @RByers, @timcappalli)
-
Define Digital Wallet w3c-fedid/digital-credentials#386 (4 comments by @hlflanagan, @marcoscaceres, @RByers, @timcappalli)
-
Make user mediation implicit and always required w3c-fedid/digital-credentials#392 (3 comments by @marcoscaceres, @mohamedamir)
-
Introduce "active promise" concept for request coordinator. w3c-fedid/digital-credentials#417 (2 comments by @marcoscaceres, @mohamedamir)
-
Add terminology section, merge in Model w3c-fedid/digital-credentials#387 (2 comments by @hlflanagan, @timcappalli)
-
Add guidance on how to handle multiple presentation request entries w3c-fedid/digital-credentials#249 (2 comments by @hlflanagan, @MasterKale)
-
w3c-fedid/digital-credentials#423 (1 comment by @w3cbot)
-
Include Digital Credential Issuance in the Spec w3c-fedid/digital-credentials#204 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#408 (1 comment by @marcoscaceres)
-
TR publications
-
2 documents published.
-
Digital Credentials published twice as a Working Draft. History of Digital Credentials
-
Past meetings
Participants
-
6 participants joined.
-
David Pham (The Washington Post) joined.
-
Aram Zucker-Scharff (The Washington Post) joined.
-
Nicholas Watson (Google LLC) joined.
-
Isaiah Inuwa (Bitwarden) joined.
-
Lluís Alfons Ariño Martin (W3C Invited Experts) joined.
-
Arnar Birgisson (Google LLC) joined.
-
-
2 participants left.
-
Monty Wiseman (W3C Invited Experts) left.
-
Frank Somich (Google LLC) left.
-
-
1 organization joined.
-
Bitwarden joined.
-
GitHub
w3c-fedid/digital-credentials
-
3 issues opened.
-
Privacy Considerations for Cross-Device Flows w3c-fedid/digital-credentials#400, by @mohamedamir.
-
Privacy Considerations for Credential Issuance w3c-fedid/digital-credentials#399, by @mohamedamir.
-
Consider adding an optional purpose field w3c-fedid/digital-credentials#398, by @RByers.
-
-
4 issues closed.
-
Proposal: Make mediation: 'required' the implicit behavior for Digital Credential API w3c-fedid/digital-credentials#384.
-
Don't require CM "mediation" to be specified explicitly (always 'required' for DC). w3c-fedid/digital-credentials#177.
-
Consider adding an optional purpose field w3c-fedid/digital-credentials#398.
-
Add a way to check what protocols are supported w3c-fedid/digital-credentials#168.
-
-
6 issues received 34 new comments.
-
Paths towards resolution on the registry [TPAC] w3c-fedid/digital-credentials#396 (13 comments by @hlflanagan, @marcoscaceres, @martinthomson, @npdoty, @RByers, @simoneonofri, @timcappalli, @wseltzer)
-
registration of and commitment to a particular use case and purpose w3c-fedid/digital-credentials#266 (9 comments by @c2bo, @mharbach, @npdoty, @RByers)
-
enumerated values for purpose, sharing and retention in API method w3c-fedid/digital-credentials#209 (5 comments by @c2bo, @npdoty, @RByers)
-
Wallet Selection Binding during Issuance w3c-fedid/digital-credentials#382 (5 comments by @erik-anderson, @npdoty, @paolo-de-rosa, @timcappalli)
-
Add a way to check what protocols are supported w3c-fedid/digital-credentials#168 (1 comment by @marcoscaceres)
-
-
2 pull requests merged.
-
Make user mediation implicit and always required w3c-fedid/digital-credentials#392.
-
Add a11y guidance for user agents w3c-fedid/digital-credentials#238.
-
-
8 pull requests received 28 new comments.
-
Make user mediation implicit and always required w3c-fedid/digital-credentials#392 (12 comments by @hlflanagan, @marcoscaceres, @mohamedamir, @npdoty, @TallTed)
-
Security Considerations: Writing first round of threats and mitigatio… w3c-fedid/digital-credentials#277 (6 comments by @marcoscaceres, @RByers, @simoneonofri, @TallTed)
-
Add terminology section, merge in Model w3c-fedid/digital-credentials#387 (3 comments by @hlflanagan, @marcoscaceres, @msporny)
-
w3c-fedid/digital-credentials#397 (1 comment by @w3cbot)
-
Security Considerations: Writing Introduction w3c-fedid/digital-credentials#272 (1 comment by @simoneonofri)
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381 (1 comment by @TallTed)
-
w3c-fedid/FedCM
-
2 issues opened.
-
New w3c-fedid/FedCM#795, by @manpowersupplieragent-art.
-
-
1 issue closed.
-
New w3c-fedid/FedCM#795.
-
-
4 issues received 14 new comments.
-
Lock subframes to same identity as parent frames w3c-fedid/FedCM#782 (9 comments by @ThisIsMissEm, @will-bartlett)
-
w3c-fedid/FedCM#317 (1 comment by @Sawsqr68)
-
Allow IdPs to initiate a FedCM flow in top level redirects without requiring changes to Relying Parties w3c-fedid/FedCM#794 (1 comment by @samuelgoto)
-
-
2 pull requests received 15 new comments.
-
Update service-workers mode to all for credentialed requests w3c-fedid/FedCM#787 (4 comments by @npm1, @pottis, @will-bartlett)
w3c-fedid/meetings
-
1 pull request opened.
-
Fix formatting in FedCM agenda document w3c-fedid/meetings#4, by @samuelgoto.
-
-
1 pull request merged.
-
Fix formatting in FedCM agenda document w3c-fedid/meetings#4.
-
TR publications
-
5 documents published.
-
Digital Credentials published 5 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
5 meetings.
Participants
-
1 participant joined.
-
Benjamin Kelly (Meta) joined.
-
-
1 participant left.
-
Zachary Tan (Google LLC) left.
-
-
2 organizations joined.
-
Meta joined.
-
The Washington Post joined.
-
GitHub
w3c-fedid/digital-credentials
-
4 issues opened.
-
Paths towards resolution on the registry [TPAC] w3c-fedid/digital-credentials#396, by @timcappalli.
-
Link up defined terms w3c-fedid/digital-credentials#394, by @marcoscaceres.
-
Clarify what to do when issuance or presentation is not supported w3c-fedid/digital-credentials#393, by @marcoscaceres.
-
Proposal: Make mediation: 'required' the implicit behavior for Digital Credential API w3c-fedid/digital-credentials#384, by @mohamedamir.
-
-
6 issues closed.
-
Invoked from disconnected document w3c-fedid/digital-credentials#112.
-
Define coordinator w3c-fedid/digital-credentials#305.
-
Relax the User Activation Requirement w3c-fedid/digital-credentials#377.
-
Define WebDriver integration w3c-fedid/digital-credentials#131.
-
Add userAgentAllowsProtocol() example w3c-fedid/digital-credentials#365.
-
Figure out a system for displaying contributors in the spec w3c-fedid/digital-credentials#311.
-
-
9 issues received 26 new comments.
-
Relax the User Activation Requirement w3c-fedid/digital-credentials#377 (11 comments by @hlflanagan, @marcoscaceres, @mharbach, @mohamedamir, @timcappalli)
-
Wallet Selection Binding during Issuance w3c-fedid/digital-credentials#382 (8 comments by @dlongley, @hlflanagan, @jandrieu, @leifj, @paulbastian, @RByers, @simoneonofri)
-
Add a way to check what protocols are supported w3c-fedid/digital-credentials#168 (1 comment by @timcappalli)
-
w3c-fedid/digital-credentials#38 (1 comment by @RByers)
-
Add error for when the API is supported, but the platform doesn't support it w3c-fedid/digital-credentials#359 (1 comment by @timcappalli)
-
Proposal: Make mediation: 'required' the implicit behavior for Digital Credential API w3c-fedid/digital-credentials#384 (1 comment by @timcappalli)
-
Add userAgentAllowsProtocol() example w3c-fedid/digital-credentials#365 (1 comment by @marcoscaceres)
-
-
6 pull requests opened.
-
Fallback to Cred Man when the API is not supported w3c-fedid/digital-credentials#395, by @marcoscaceres.
-
Make user mediation implicit and always required w3c-fedid/digital-credentials#392, by @mohamedamir.
-
Editorial: Fix sentence structure w3c-fedid/digital-credentials#390, by @mohamedamir.
-
Editorial: add Index section w3c-fedid/digital-credentials#389, by @marcoscaceres.
-
Add terminology section, merge in Model w3c-fedid/digital-credentials#387, by @timcappalli.
-
Define Digital Wallet w3c-fedid/digital-credentials#386, by @marcoscaceres.
-
-
5 pull requests merged.
-
chore: move old pdfs to proposals w3c-fedid/digital-credentials#330.
-
Editorial: add Index section w3c-fedid/digital-credentials#389.
-
Editorial: Fix sentence structure w3c-fedid/digital-credentials#390.
-
Define interaction between platform credential chooser and the user agent w3c-fedid/digital-credentials#306.
-
Editorial: update acknowledgements section w3c-fedid/digital-credentials#358.
-
-
14 pull requests received 204 new comments.
-
Add terminology section, merge in Model w3c-fedid/digital-credentials#387 (63 comments by @marcoscaceres, @MasterKale, @msporny, @tidoust, @timcappalli)
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381 (46 comments by @marcoscaceres, @mohamedamir, @TallTed, @timcappalli)
-
Define interaction between platform credential chooser and the user agent w3c-fedid/digital-credentials#306 (39 comments by @hlflanagan, @marcoscaceres, @mohamedamir, @TallTed, @timcappalli)
-
Define Digital Wallet w3c-fedid/digital-credentials#386 (34 comments by @marcoscaceres, @mohamedamir, @msporny, @TallTed, @timcappalli)
-
Make user mediation implicit and always required w3c-fedid/digital-credentials#392 (9 comments by @marcoscaceres, @mohamedamir)
-
Fallback to Cred Man when the API is not supported w3c-fedid/digital-credentials#395 (2 comments by @marcoscaceres)
-
Editorial: Fix sentence structure w3c-fedid/digital-credentials#390 (2 comments by @marcoscaceres, @mohamedamir)
-
w3c-fedid/digital-credentials#388 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#383 (1 comment by @w3cbot)
-
Editorial: update acknowledgements section w3c-fedid/digital-credentials#358 (1 comment by @MasterKale)
-
w3c-fedid/FedCM
-
3 issues opened.
-
Incremental authentication/authorization w3c-fedid/FedCM#793, by @stianst.
-
Is https://w3c-fedid.github.io/FedCM/#issue-f83eac19 still accurate? w3c-fedid/FedCM#791, by @miketaylr.
-
Add files to repository w3c-fedid/FedCM#788, by @tylorjohnson09.
-
-
3 issues closed.
-
Is https://w3c-fedid.github.io/FedCM/#issue-f83eac19 still accurate? w3c-fedid/FedCM#791.
-
Add files to repository w3c-fedid/FedCM#788.
-
Support showing iframe origins in the UI, when they are third-party w3c-fedid/FedCM#725.
-
-
6 issues received 12 new comments.
-
Is https://w3c-fedid.github.io/FedCM/#issue-f83eac19 still accurate? w3c-fedid/FedCM#791 (2 comments by @cbiesinger, @miketaylr)
-
2 pull requests opened.
-
Revamp intro w3c-fedid/FedCM#792, by @npm1.
-
Update service-workers mode to all for credentialed requests w3c-fedid/FedCM#787, by @will-bartlett.
-
-
1 pull request merged.
-
[FedCM] Specify third party iframe display support w3c-fedid/FedCM#774.
-
-
4 pull requests received 28 new comments.
-
Update service-workers mode to all for credentialed requests w3c-fedid/FedCM#787 (8 comments by @cbiesinger, @EmLauber, @npm1, @TallTed, @will-bartlett)
-
[FedCM] Specify third party iframe display support w3c-fedid/FedCM#774 (8 comments by @cbiesinger, @npm1)
-
feat: Add support for passing arbitrary parameters to the ID assertio… w3c-fedid/FedCM#766 (2 comments by @npm1, @tylorjohnson09)
TR publications
-
5 documents published.
-
Digital Credentials published 5 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
7 meetings.
Participants
-
7 participants joined.
-
Srdjan Marinvoic (Futurae Technologies AG) joined.
-
Frederik Krogsdal Jacobsen (Idura) joined.
-
George Fletcher (W3C Invited Experts) joined.
-
Gorman Ho (Okta) joined.
-
Peter Zenzerovich (Microsoft Corporation) joined.
-
William Bartlett (Microsoft Corporation) joined.
-
Natalia Markoborodova (Google LLC) joined.
-
-
1 participant left.
-
Zachary Cancio (Google LLC) left.
-
-
1 organization joined.
-
Futurae Technologies AG joined.
-
GitHub
w3c-fedid/FedCM
-
3 issues opened.
-
Lock subframes to same identity as parent frames w3c-fedid/FedCM#782, by @will-bartlett.
-
Say something about caching w3c-fedid/FedCM#781, by @will-bartlett.
-
IdentityCredentialError: code vs error property w3c-fedid/FedCM#780, by @Elchi3.
-
-
3 issues closed.
-
IdentityCredentialError: code vs error property w3c-fedid/FedCM#780.
-
10 issues received 34 new comments.
-
Say something about caching w3c-fedid/FedCM#781 (4 comments by @cbiesinger, @will-bartlett, @wseltzer)
-
Lack of generic params on login_url is limiting, unclear privacy value w3c-fedid/FedCM#778 (4 comments by @npm1, @philsmart, @wseltzer)
-
Support chained authentication flows before reducing heuristics and classifications/lists in navigational tracking mitigations w3c-fedid/FedCM#618 (4 comments by @philsmart, @samuelgoto, @wseltzer)
-
Extension to FedCM API to allow SAML or OIDC frontchannel logout w3c-fedid/FedCM#773 (2 comments by @huebnd, @johannhof)
-
`globalObject`s should be the top level window, rather than the cross site iframe when Permissions Policy is used w3c-fedid/FedCM#729 (2 comments by @cbiesinger, @EmLauber)
-
w3c-fedid/FedCM#83 (1 comment by @will-bartlett)
-
3 pull requests opened.
-
Update to explainer for Structured data support w3c-fedid/FedCM#786, by @pottis.
-
Explainer structured object w3c-fedid/FedCM#785, by @pottis.
-
Explainer on Structured token format w3c-fedid/FedCM#783, by @pottis.
-
-
2 pull requests merged.
-
Update to explainer for Structured data support w3c-fedid/FedCM#786.
-
Explainer on Structured token format w3c-fedid/FedCM#783.
-
-
1 pull request closed.
-
Explainer structured object w3c-fedid/FedCM#785.
-
-
4 pull requests received 27 new comments.
-
[FedCM] Specify third party iframe display support w3c-fedid/FedCM#774 (9 comments by @cbiesinger, @npm1)
w3c-fedid/digital-credentials
-
4 issues opened.
-
Wallet Selection Binding during Issuance w3c-fedid/digital-credentials#382, by @leecam.
-
Relax the User Activation Requirement w3c-fedid/digital-credentials#377, by @QZHelen.
-
Cross-origin mitigations can't be enforced at the wallet layer when multiple wallets are used w3c-fedid/digital-credentials#374, by @kdenhartog.
-
Add details about the Cross-device experience for the Digital Credentials API w3c-fedid/digital-credentials#369, by @mohamedamir.
-
-
6 issues closed.
-
Add feature detection example w3c-fedid/digital-credentials#366.
-
Revise the explainer w3c-fedid/digital-credentials#367.
-
Clarify that platform interactions are out of scope w3c-fedid/digital-credentials#321.
-
proof of authentication w3c-fedid/digital-credentials#296.
-
write security considerations w3c-fedid/digital-credentials#184.
-
Rework abstract, scope, and introduction w3c-fedid/digital-credentials#68.
-
-
9 issues received 23 new comments.
-
Cross-origin mitigations can't be enforced at the wallet layer when multiple wallets are used w3c-fedid/digital-credentials#374 (10 comments by @kdenhartog, @marcoscaceres, @timcappalli)
-
Add details about the Cross-device experience for the Digital Credentials API w3c-fedid/digital-credentials#369 (3 comments by @marcoscaceres, @timcappalli)
-
Update scope around issuance/create to be specific to credential manager selection w3c-fedid/digital-credentials#343 (1 comment by @marcoscaceres)
-
Most users will experience a no-matching-credential dead-end w3c-fedid/digital-credentials#104 (1 comment by @marcoscaceres)
-
-
7 pull requests opened.
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381, by @mohamedamir.
-
chore: temporary removing validating links w3c-fedid/digital-credentials#380, by @simoneonofri.
-
Update auto-publish.yml to yes latest spec-prod w3c-fedid/digital-credentials#379, by @mohamedamir.
-
fix: broken link and update openid references to final w3c-fedid/digital-credentials#378, by @c2bo.
-
Remove registry w3c-fedid/digital-credentials#376, by @timcappalli.
-
Get steps w3c-fedid/digital-credentials#372, by @marcoscaceres.
-
Editorial: Add feature and protocol detection examples w3c-fedid/digital-credentials#371, by @timcappalli.
-
-
7 pull requests merged.
-
fix: broken link and update openid references to final w3c-fedid/digital-credentials#378.
-
chore: temporary removing validating links w3c-fedid/digital-credentials#380.
-
Editorial: Add feature and protocol detection examples w3c-fedid/digital-credentials#371.
-
docs(explainer): Update the explainer to include digital credential issuance w3c-fedid/digital-credentials#364.
-
docs(explainer): Changes to Explainer: Weakening Claims on Privacy and Transparency w3c-fedid/digital-credentials#368.
-
Limit scope to UA boundary w3c-fedid/digital-credentials#344.
-
Editorial: clean up scope section w3c-fedid/digital-credentials#339.
-
-
1 pull request closed.
-
Update auto-publish.yml to yes latest spec-prod w3c-fedid/digital-credentials#379.
-
-
11 pull requests received 103 new comments.
-
Editorial: Add feature and protocol detection examples w3c-fedid/digital-credentials#371 (28 comments by @marcoscaceres, @MasterKale, @TallTed)
-
Define interaction between platform credential chooser and the user agent w3c-fedid/digital-credentials#306 (21 comments by @marcoscaceres, @TallTed)
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381 (12 comments by @marcoscaceres, @TallTed)
-
Add a11y guidance for user agents w3c-fedid/digital-credentials#238 (11 comments by @c2bo, @marcoscaceres, @MasterKale, @mohamedamir, @simoneonofri, @wseltzer)
-
Add guidance on how to handle multiple presentation request entries w3c-fedid/digital-credentials#249 (9 comments by @marcoscaceres, @TallTed, @wseltzer)
-
docs(explainer): Changes to Explainer: Weakening Claims on Privacy and Transparency w3c-fedid/digital-credentials#368 (8 comments by @marcoscaceres, @mohamedamir)
-
docs(explainer): Update the explainer to include digital credential issuance w3c-fedid/digital-credentials#364 (7 comments by @marcoscaceres, @mohamedamir)
-
Limit scope to UA boundary w3c-fedid/digital-credentials#344 (3 comments by @marcoscaceres, @wseltzer)
-
Editorial: update acknowledgements section w3c-fedid/digital-credentials#358 (2 comments by @marcoscaceres)
-
w3c-fedid/digital-credentials#373 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#370 (1 comment by @w3cbot)
-
TR publications
-
10 documents published.
-
Digital Credentials published 10 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
8 meetings.
Participants
-
2 participants joined.
-
Joe Andrieu (Legendary Requirements) joined.
-
Frederik Mennes (OneSpan) joined.
-
-
1 participant left.
-
Steve Venema (Microsoft Corporation) left.
-
-
1 organization joined.
-
Legendary Requirements joined.
-
GitHub
w3c-fedid/FedCM
-
8 issues opened.
-
Make it clear image fetches in the spec are uncredentialed w3c-fedid/FedCM#779, by @npm1.
-
Lack of generic params on login_url is limiting, unclear privacy value w3c-fedid/FedCM#778, by @will-bartlett.
-
Manifest fingerprinting wording describes mitigation imprecisely w3c-fedid/FedCM#777, by @will-bartlett.
-
Manifest fingerprinting via subdomains and public suffix list w3c-fedid/FedCM#776, by @will-bartlett.
-
Manifest fingerprinting using branding icon w3c-fedid/FedCM#775, by @will-bartlett.
-
Extension to FedCM API to allow SAML or OIDC frontchannel logout w3c-fedid/FedCM#773, by @huebnd.
-
MbAsabAlii w3c-fedid/FedCM#772, by @rajrajuraihan987-create.
-
Yy w3c-fedid/FedCM#769, by @hannahjason407-crypto.
-
-
3 issues closed.
-
Manifest fingerprinting using branding icon w3c-fedid/FedCM#775.
-
MbAsabAlii w3c-fedid/FedCM#772.
-
Yy w3c-fedid/FedCM#769.
-
-
13 issues received 49 new comments.
-
Extension to FedCM API to allow SAML or OIDC frontchannel logout w3c-fedid/FedCM#773 (8 comments by @huebnd, @johannhof, @samuelgoto)
-
Lack of generic params on login_url is limiting, unclear privacy value w3c-fedid/FedCM#778 (5 comments by @npm1, @samuelgoto, @will-bartlett)
-
Manifest fingerprinting via subdomains and public suffix list w3c-fedid/FedCM#776 (4 comments by @npm1, @samuelgoto, @will-bartlett)
-
Support chained authentication flows before reducing heuristics and classifications/lists in navigational tracking mitigations w3c-fedid/FedCM#618 (4 comments by @hlflanagan, @philsmart)
-
Support showing iframe origins in the UI, when they are third-party w3c-fedid/FedCM#725 (4 comments by @bvandersloot-mozilla, @cbiesinger, @hlflanagan)
-
Manifest fingerprinting wording describes mitigation imprecisely w3c-fedid/FedCM#777 (3 comments by @npm1, @will-bartlett)
-
Manifest fingerprinting using branding icon w3c-fedid/FedCM#775 (2 comments by @npm1, @will-bartlett)
-
Make it clear image fetches in the spec are uncredentialed w3c-fedid/FedCM#779 (1 comment by @cbiesinger)
-
`globalObject`s should be the top level window, rather than the cross site iframe when Permissions Policy is used w3c-fedid/FedCM#729 (1 comment by @cbiesinger)
-
3 pull requests opened.
-
[FedCM] Specify third party iframe display support w3c-fedid/FedCM#774, by @cbiesinger.
-
FedCM Object Token Enhancement w3c-fedid/FedCM#771, by @pottis.
-
Deprecate nonce parameter w3c-fedid/FedCM#768, by @pottis.
-
-
2 pull requests merged.
-
FedCM Object Token Enhancement w3c-fedid/FedCM#771.
-
Deprecate nonce parameter w3c-fedid/FedCM#768.
-
-
2 pull requests closed.
-
FedCM Object Token Enhancement Proposal w3c-fedid/FedCM#761.
-
FedCM nonce Parameter Deprecation Specification w3c-fedid/FedCM#762.
-
-
5 pull requests received 78 new comments.
-
FedCM Object Token Enhancement w3c-fedid/FedCM#771 (63 comments by @aaronpk, @cbiesinger, @domfarolino, @mooreds, @npm1, @pottis, @TallTed)
-
[FedCM] Specify third party iframe display support w3c-fedid/FedCM#774 (4 comments by @cbiesinger, @npm1, @TallTed)
-
w3c-fedid/digital-credentials
-
19 issues opened.
-
Revise the explainer w3c-fedid/digital-credentials#367, by @mohamedamir.
-
Add feature detection example w3c-fedid/digital-credentials#366, by @marcoscaceres.
-
Add userAgentAllowsProtocol() example w3c-fedid/digital-credentials#365, by @marcoscaceres.
-
explainer: fix "do nothing" link w3c-fedid/digital-credentials#363, by @npdoty.
-
Revise introduction and abstract w3c-fedid/digital-credentials#361, by @marcoscaceres.
-
Redo security considerations w3c-fedid/digital-credentials#360, by @marcoscaceres.
-
Add error for when the API is supported, but the platform doesn't support it w3c-fedid/digital-credentials#359, by @marcoscaceres.
-
Add means to test Digital Credentials API w3c-fedid/digital-credentials#357, by @mohamedamir.
-
Add DigitalCredentialIssuanceResponse partial w3c-fedid/digital-credentials#356, by @timcappalli.
-
Add a terminology section w3c-fedid/digital-credentials#352, by @timcappalli.
-
Ensure that credential issuers do not discriminate based on the user’s device or OS w3c-fedid/digital-credentials#349, by @DemiMarie.
-
Security considerations don't relate directly to the spec w3c-fedid/digital-credentials#346, by @marcoscaceres.
-
Is a registry needed? w3c-fedid/digital-credentials#345, by @jandrieu.
-
Update scope around issuance/create to be specific to credential manager selection w3c-fedid/digital-credentials#343, by @timcappalli.
-
Top frame origin should be passed to client platforms and credential managers for cross-origin requests w3c-fedid/digital-credentials#333, by @timcappalli.
-
Add guidance to verifiers/issuers and clients/client platforms on cross-origin usage w3c-fedid/digital-credentials#332, by @timcappalli.
-
iframe usage text doesn't make sense w3c-fedid/digital-credentials#331, by @timcappalli.
-
Do we need a permissions policy for third-party frames for issuance? w3c-fedid/digital-credentials#327, by @mohamedamir.
-
Clarify that platform interactions are out of scope w3c-fedid/digital-credentials#321, by @marcoscaceres.
-
-
8 issues closed.
-
[Discussion] Integrate with web wallets? w3c-fedid/digital-credentials#38.
-
Editorial: Add references to definitions in the privacy considerations w3c-fedid/digital-credentials#284.
-
Credential Management integration w3c-fedid/digital-credentials#65.
-
custom-schemes.md: point 7 should discuss how a browser api could avoid or mitigate this problem w3c-fedid/digital-credentials#40.
-
iframe usage text doesn't make sense w3c-fedid/digital-credentials#331.
-
Do we need a permissions policy for third-party frames for issuance? w3c-fedid/digital-credentials#327.
-
explainer describes issuance as out of scope w3c-fedid/digital-credentials#316.
-
Consider Verifiable Presentation Request design patterns w3c-fedid/digital-credentials#12.
-
-
1 issue reopened.
-
Figure out a system for displaying contributors in the spec w3c-fedid/digital-credentials#311, by @MasterKale.
-
-
22 issues received 53 new comments.
-
Ensure that credential issuers do not discriminate based on the user’s device or OS w3c-fedid/digital-credentials#349 (5 comments by @DemiMarie, @timcappalli)
-
Figure out a system for displaying contributors in the spec w3c-fedid/digital-credentials#311 (4 comments by @hlflanagan, @marcoscaceres, @MasterKale)
-
user agents should limit to protocols listed in the registry that meet the group's requirements w3c-fedid/digital-credentials#288 (4 comments by @marcoscaceres, @mohamedamir, @npdoty)
-
Add means to test Digital Credentials API w3c-fedid/digital-credentials#357 (2 comments by @hlflanagan, @timcappalli)
-
Add a terminology section w3c-fedid/digital-credentials#352 (2 comments by @marcoscaceres, @TallTed)
-
Most users will experience a no-matching-credential dead-end w3c-fedid/digital-credentials#104 (2 comments by @marcoscaceres, @mohamedamir)
-
Add guidance to verifiers/issuers and clients/client platforms on cross-origin usage w3c-fedid/digital-credentials#332 (2 comments by @hlflanagan, @npdoty)
-
enumerated values for purpose, sharing and retention in API method w3c-fedid/digital-credentials#209 (1 comment by @hlflanagan)
-
require in-context in-content explanation and an element for user-initiated presentation w3c-fedid/digital-credentials#208 (1 comment by @hlflanagan)
-
Update scope around issuance/create to be specific to credential manager selection w3c-fedid/digital-credentials#343 (1 comment by @mohamedamir)
-
w3c-fedid/digital-credentials#44 (1 comment by @hlflanagan)
-
Top frame origin should be passed to client platforms and credential managers for cross-origin requests w3c-fedid/digital-credentials#333 (1 comment by @hlflanagan)
-
Consider applying the robustness principle with regard to user agent request validation w3c-fedid/digital-credentials#100 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#65 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#40 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#12 (1 comment by @marcoscaceres)
-
26 pull requests opened.
-
docs(explainer): Changes to Explainer: Weakening Claims on Privacy and Transparency w3c-fedid/digital-credentials#368, by @mohamedamir.
-
docs(explainer): Update the explainer to include digital credential issuance w3c-fedid/digital-credentials#364, by @mohamedamir.
-
Remove redundant text in index.html w3c-fedid/digital-credentials#362, by @matatk.
-
Editorial: update acknowledgements section w3c-fedid/digital-credentials#358, by @bc-pi.
-
chore(explainer): fix link to risk.md from ping w3c-fedid/digital-credentials#354, by @marcoscaceres.
-
chore: link up various key terms w3c-fedid/digital-credentials#353, by @marcoscaceres.
-
chore: bring back the missing </section> tag w3c-fedid/digital-credentials#350, by @mohamedamir.
-
chore: remove unnecessary section tag w3c-fedid/digital-credentials#348, by @marcoscaceres.
-
Editorial: mark some sections as informative w3c-fedid/digital-credentials#347, by @marcoscaceres.
-
Limit scope to UA boundary w3c-fedid/digital-credentials#344, by @marcoscaceres.
-
chore(README): add useful links w3c-fedid/digital-credentials#342, by @marcoscaceres.
-
chore: fix links pointing to old repo w3c-fedid/digital-credentials#341, by @marcoscaceres.
-
Editorial: fix link to priv/sec questionnaire w3c-fedid/digital-credentials#340, by @marcoscaceres.
-
Editorial: clean up scope section w3c-fedid/digital-credentials#339, by @marcoscaceres.
-
Editorial: make digital wallets out of scope w3c-fedid/digital-credentials#338, by @marcoscaceres.
-
Editorial: Fix mislabeling of section intended for non-government credentials w3c-fedid/digital-credentials#336, by @csarven.
-
Editorial: Fix cross-origin usage example text w3c-fedid/digital-credentials#335, by @timcappalli.
-
chore: move old pdfs to proposals w3c-fedid/digital-credentials#330, by @marcoscaceres.
-
chore: Delete horizontal-reviews/security-privacy.md w3c-fedid/digital-credentials#329, by @marcoscaceres.
-
Add Permissions Policy for DC Issuance w3c-fedid/digital-credentials#328, by @mohamedamir.
-
Chore: add section markers w3c-fedid/digital-credentials#326, by @marcoscaceres.
-
Editorial: fix SoTD and some typos w3c-fedid/digital-credentials#325, by @marcoscaceres.
-
Editorial: move examples to own section w3c-fedid/digital-credentials#324, by @marcoscaceres.
-
README: make readme more focused. w3c-fedid/digital-credentials#323, by @marcoscaceres.
-
Explainer: point to spec for scope and permissions policy w3c-fedid/digital-credentials#322, by @marcoscaceres.
-
Editorial: move scope w3c-fedid/digital-credentials#320, by @marcoscaceres.
-
-
21 pull requests merged.
-
Editorial: make digital wallets out of scope w3c-fedid/digital-credentials#338.
-
Remove redundant text in index.html w3c-fedid/digital-credentials#362.
-
chore: fix links pointing to old repo w3c-fedid/digital-credentials#341.
-
chore(explainer): fix link to risk.md from ping w3c-fedid/digital-credentials#354.
-
chore(README): add useful links w3c-fedid/digital-credentials#342.
-
chore: link up various key terms w3c-fedid/digital-credentials#353.
-
chore: bring back the missing </section> tag w3c-fedid/digital-credentials#350.
-
Editorial: mark some sections as informative w3c-fedid/digital-credentials#347.
-
chore: remove unnecessary section tag w3c-fedid/digital-credentials#348.
-
Editorial: Add Acknowledgements section w3c-fedid/digital-credentials#314.
-
Editorial: fix link to priv/sec questionnaire w3c-fedid/digital-credentials#340.
-
chore: Delete horizontal-reviews/security-privacy.md w3c-fedid/digital-credentials#329.
-
Editorial: Fix cross-origin usage example text w3c-fedid/digital-credentials#335.
-
Editorial: Fix mislabeling of section intended for non-government credentials w3c-fedid/digital-credentials#336.
-
Add Permissions Policy for DC Issuance w3c-fedid/digital-credentials#328.
-
README: make readme more focused. w3c-fedid/digital-credentials#323.
-
Explainer: point to spec for scope and permissions policy w3c-fedid/digital-credentials#322.
-
Chore: add section markers w3c-fedid/digital-credentials#326.
-
Editorial: fix SoTD and some typos w3c-fedid/digital-credentials#325.
-
Editorial: move scope w3c-fedid/digital-credentials#320.
-
Editorial: move examples to own section w3c-fedid/digital-credentials#324.
-
-
1 pull request closed.
-
Add request validation w3c-fedid/digital-credentials#156.
-
-
25 pull requests received 183 new comments.
-
Define interaction between platform credential chooser and the user agent w3c-fedid/digital-credentials#306 (26 comments by @hlflanagan, @marcoscaceres, @mohamedamir, @TallTed)
-
Editorial: clean up scope section w3c-fedid/digital-credentials#339 (20 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
Add guidance on how to handle multiple presentation request entries w3c-fedid/digital-credentials#249 (16 comments by @MasterKale, @TallTed)
-
docs(explainer): Update the explainer to include digital credential issuance w3c-fedid/digital-credentials#364 (16 comments by @mohamedamir, @npdoty, @TallTed, @timcappalli)
-
Editorial: Add Acknowledgements section w3c-fedid/digital-credentials#314 (16 comments by @bc-pi, @marcoscaceres, @MasterKale, @TallTed)
-
Add Permissions Policy for DC Issuance w3c-fedid/digital-credentials#328 (16 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
Add a11y guidance for user agents w3c-fedid/digital-credentials#238 (11 comments by @marcoscaceres, @MasterKale, @mohamedamir)
-
chore: fix links pointing to old repo w3c-fedid/digital-credentials#341 (9 comments by @c2bo, @marcoscaceres, @mohamedamir, @TallTed, @timcappalli)
-
Limit scope to UA boundary w3c-fedid/digital-credentials#344 (9 comments by @marcoscaceres, @mohamedamir, @TallTed, @timcappalli)
-
chore(explainer): fix link to risk.md from ping w3c-fedid/digital-credentials#354 (7 comments by @marcoscaceres, @npdoty, @simoneonofri, @TallTed)
-
Add request validation w3c-fedid/digital-credentials#156 (6 comments by @c2bo, @hlflanagan, @marcoscaceres)
-
Editorial: update acknowledgements section w3c-fedid/digital-credentials#358 (5 comments by @bc-pi, @marcoscaceres, @MasterKale, @TallTed)
-
Editorial: make digital wallets out of scope w3c-fedid/digital-credentials#338 (5 comments by @hlflanagan, @marcoscaceres, @TallTed, @timcappalli)
-
chore: move old pdfs to proposals w3c-fedid/digital-credentials#330 (4 comments by @c2bo, @marcoscaceres, @timcappalli)
-
README: make readme more focused. w3c-fedid/digital-credentials#323 (4 comments by @marcoscaceres, @npdoty, @TallTed)
-
chore: link up various key terms w3c-fedid/digital-credentials#353 (2 comments by @marcoscaceres, @TallTed)
-
chore: Delete horizontal-reviews/security-privacy.md w3c-fedid/digital-credentials#329 (2 comments by @c2bo, @marcoscaceres)
-
w3c-fedid/digital-credentials#355 (1 comment by @TallTed)
-
w3c-fedid/digital-credentials#351 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#337 (1 comment by @w3cbot)
-
Editorial: Fix cross-origin usage example text w3c-fedid/digital-credentials#335 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#334 (1 comment by @marcoscaceres)
-
Explainer: point to spec for scope and permissions policy w3c-fedid/digital-credentials#322 (1 comment by @marcoscaceres)
-
w3c-fedid/login-status
-
1 issue opened.
-
Service workers should be allowed to use login.setStatus w3c-fedid/login-status#10, by @cbiesinger.
-
TR publications
-
3 documents published.
-
Digital Credentials published twice as a Working Draft. History of Digital Credentials
-
Digital Credentials published as a First Public Working Draft. History of Digital Credentials
-
Past meetings
GitHub
w3c-fedid/FedCM
-
5 issues opened.
-
Nothing w3c-fedid/FedCM#767, by @proputon261-design.
-
Specify the border between FedCM and protocols building on it w3c-fedid/FedCM#764, by @togamid.
-
Define "params" and "fields" semantics in Section 2.4 w3c-fedid/FedCM#763, by @togamid.
-
New ksss w3c-fedid/FedCM#759, by @Botgroupj.
-
Allow IDPs to block invalid client IDs w3c-fedid/FedCM#758, by @cbiesinger.
-
-
8 issues closed.
-
Nothing w3c-fedid/FedCM#767.
-
IDP section is non-normative and out of date w3c-fedid/FedCM#753.
-
Tracking through IDP with individualized account and client_metadata endpoints w3c-fedid/FedCM#700.
-
New ksss w3c-fedid/FedCM#759.
-
concerns about email in Accounts List w3c-fedid/FedCM#317.
-
login_url not documented in Section 3.2 w3c-fedid/FedCM#697.
-
Wrong Web IDL type for URLs in Federated Credential Management API w3c-fedid/FedCM#754.
-
-
12 issues received 56 new comments.
-
Specify the border between FedCM and protocols building on it w3c-fedid/FedCM#764 (6 comments by @aaronpk, @hlflanagan, @npm1, @togamid)
-
Support showing iframe origins in the UI, when they are third-party w3c-fedid/FedCM#725 (5 comments by @bvandersloot-mozilla, @cbiesinger, @hlflanagan)
-
Allow IDPs to block invalid client IDs w3c-fedid/FedCM#758 (4 comments by @bvandersloot-mozilla, @cbiesinger, @hlflanagan)
-
Support chained authentication flows before reducing heuristics and classifications/lists in navigational tracking mitigations w3c-fedid/FedCM#618 (2 comments by @philsmart, @wseltzer)
-
`globalObject`s should be the top level window, rather than the cross site iframe when Permissions Policy is used w3c-fedid/FedCM#729 (2 comments by @bvandersloot-mozilla, @cbiesinger)
-
Tracking through IDP with individualized account and client_metadata endpoints w3c-fedid/FedCM#700 (1 comment by @wseltzer)
-
w3c-fedid/FedCM#407 (1 comment by @wseltzer)
-
7 pull requests opened.
-
feat: Add support for passing arbitrary parameters to the ID assertio… w3c-fedid/FedCM#766, by @tylorjohnson09.
-
FedCM nonce Parameter Deprecation Specification w3c-fedid/FedCM#762, by @pottis.
-
FedCM Object Token Enhancement Proposal w3c-fedid/FedCM#761, by @pottis.
-
Add another well-known check w3c-fedid/FedCM#760, by @npm1.
-
Synchronize IdP section with rest of spec w3c-fedid/FedCM#757, by @togamid.
-
Pass IdentityProviderConfig to `fetch the config file` w3c-fedid/FedCM#756, by @npm1.
-
Update errors to USVString w3c-fedid/FedCM#755, by @npm1.
-
-
4 pull requests merged.
-
Add another well-known check w3c-fedid/FedCM#760.
-
Synchronize IdP section with rest of spec w3c-fedid/FedCM#757.
-
Pass IdentityProviderConfig to `fetch the config file` w3c-fedid/FedCM#756.
-
Update errors to USVString w3c-fedid/FedCM#755.
-
-
6 pull requests received 107 new comments.
-
FedCM Object Token Enhancement Proposal w3c-fedid/FedCM#761 (45 comments by @hlflanagan, @npm1, @pottis, @TallTed, @togamid)
-
FedCM nonce Parameter Deprecation Specification w3c-fedid/FedCM#762 (33 comments by @aaronpk, @cbiesinger, @hlflanagan, @npm1, @pottis, @TallTed, @togamid)
-
feat: Add support for passing arbitrary parameters to the ID assertio… w3c-fedid/FedCM#766 (2 comments by @npm1)
-
w3c-fedid/digital-credentials
-
5 issues opened.
-
Make `requests` member required for `DigitalCredentialCreationOptions` w3c-fedid/digital-credentials#319, by @mohamedamir.
-
Can Selective Disclosure Be Expanded? w3c-fedid/digital-credentials#317, by @zoracon.
-
explainer describes issuance as out of scope w3c-fedid/digital-credentials#316, by @npdoty.
-
examples or explainability about what might be in the `data` parameters w3c-fedid/digital-credentials#315, by @npdoty.
-
Figure out a system for displaying contributors in the spec w3c-fedid/digital-credentials#311, by @MasterKale.
-
-
5 issues closed.
-
Make `requests` member required for `DigitalCredentialCreationOptions` w3c-fedid/digital-credentials#319.
-
Can Selective Disclosure Be Expanded? w3c-fedid/digital-credentials#317.
-
Make `requests` member `required` for DigitalCredentialRequestOptions w3c-fedid/digital-credentials#210.
-
[spec] DigitalCredentialRequestOptions and DigitalCredential objects must be JSON serializable w3c-fedid/digital-credentials#125.
-
Spec should group API section w3c-fedid/digital-credentials#303.
-
-
11 issues received 22 new comments.
-
user agents should limit to protocols listed in the registry that meet the group's requirements w3c-fedid/digital-credentials#288 (6 comments by @jandrieu, @npdoty, @simoneonofri, @TallTed)
-
Can Selective Disclosure Be Expanded? w3c-fedid/digital-credentials#317 (5 comments by @timcappalli, @zoracon)
-
Privacy Considerations: Addressing "unnecessary" usage of the API w3c-fedid/digital-credentials#243 (2 comments by @kdenhartog, @zoracon)
-
w3c-fedid/digital-credentials#38 (1 comment by @charsleysa)
-
examples or explainability about what might be in the `data` parameters w3c-fedid/digital-credentials#315 (1 comment by @TallTed)
-
explainer describes issuance as out of scope w3c-fedid/digital-credentials#316 (1 comment by @wseltzer)
-
Add OpenID for Verifiable Presentations (OpenID4VP) to registry w3c-fedid/digital-credentials#211 (1 comment by @bc-pi)
-
Figure out a system for displaying contributors in the spec w3c-fedid/digital-credentials#311 (1 comment by @MasterKale)
-
w3c-fedid/digital-credentials#65 (1 comment by @simoneonofri)
-
-
7 pull requests opened.
-
Mark `requests` as required in DigitalCredentialCreationOptions w3c-fedid/digital-credentials#318, by @mohamedamir.
-
Editorial: Add Acknowledgements section w3c-fedid/digital-credentials#314, by @MasterKale.
-
Update Security and privacy principles w3c-fedid/digital-credentials#313, by @RByers.
-
chore: setup auto publish w3c-fedid/digital-credentials#312, by @marcoscaceres.
-
Update TAG Security & Privacy Questionnaire w3c-fedid/digital-credentials#310, by @johannhof.
-
docs(explainer.md): remove example. Point to spec. w3c-fedid/digital-credentials#309, by @marcoscaceres.
-
Make DigitalCredentialRequestOptions.requests a required member w3c-fedid/digital-credentials#308, by @marcoscaceres.
-
-
8 pull requests merged.
-
Mark `requests` as required in DigitalCredentialCreationOptions w3c-fedid/digital-credentials#318.
-
chore: setup auto publish w3c-fedid/digital-credentials#312.
-
Update Security and privacy principles w3c-fedid/digital-credentials#313.
-
docs(explainer.md): remove example. Point to spec. w3c-fedid/digital-credentials#309.
-
Update TAG Security & Privacy Questionnaire w3c-fedid/digital-credentials#310.
-
Make DigitalCredentialRequestOptions.requests a required member w3c-fedid/digital-credentials#308.
-
Require JSON serialization checks coming in w3c-fedid/digital-credentials#179.
-
Editorial: add API section w3c-fedid/digital-credentials#304.
-
-
14 pull requests received 101 new comments.
-
Define interaction between platform credential chooser and the user agent w3c-fedid/digital-credentials#306 (22 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
Editorial: Add Acknowledgements section w3c-fedid/digital-credentials#314 (16 comments by @hober, @marcoscaceres, @MasterKale, @TallTed, @wseltzer)
-
Update TAG Security & Privacy Questionnaire w3c-fedid/digital-credentials#310 (16 comments by @johannhof, @marcoscaceres, @RByers, @TallTed)
-
Add request validation w3c-fedid/digital-credentials#156 (12 comments by @bc-pi, @c2bo, @marcoscaceres, @mohamedamir, @timcappalli)
-
chore: setup auto publish w3c-fedid/digital-credentials#312 (10 comments by @marcoscaceres, @mohamedamir, @simoneonofri)
-
Add guidance on how to handle multiple presentation request entries w3c-fedid/digital-credentials#249 (7 comments by @marcoscaceres, @MasterKale, @npdoty, @TallTed, @wseltzer)
-
Add a11y guidance for user agents w3c-fedid/digital-credentials#238 (6 comments by @marcoscaceres, @MasterKale, @mohamedamir, @TallTed)
-
Update Security and privacy principles w3c-fedid/digital-credentials#313 (3 comments by @RByers, @TallTed)
-
Editorial: add API section w3c-fedid/digital-credentials#304 (3 comments by @marcoscaceres, @mohamedamir, @timcappalli)
-
Make DigitalCredentialRequestOptions.requests a required member w3c-fedid/digital-credentials#308 (2 comments by @marcoscaceres, @mohamedamir)
-
docs(explainer.md): remove example. Point to spec. w3c-fedid/digital-credentials#309 (1 comment by @timcappalli)
-
Require JSON serialization checks coming in w3c-fedid/digital-credentials#179 (1 comment by @marcoscaceres)
-
Security Considerations: Writing Introduction w3c-fedid/digital-credentials#272 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#307 (1 comment by @w3cbot)
-
Past meetings
-
7 meetings.
Participants
-
5 participants joined.
-
Monty Wiseman (W3C Invited Experts) joined.
-
Chris Needham (British Broadcasting Corporation) joined.
-
Ryan Watkins (Mastercard Incorporated) joined.
-
David Moore (IBM Corporation) joined.
-
Sandor Major (Google LLC) joined.
-
-
2 organizations joined.
-
British Broadcasting Corporation joined.
-
IBM Corporation joined.
-
GitHub
w3c-fedid/digital-credentials
-
33 issues opened.
-
Define coordinator w3c-fedid/digital-credentials#305, by @marcoscaceres.
-
Spec should group API section w3c-fedid/digital-credentials#303, by @marcoscaceres.
-
mitigations for tracking and fingerprinting using presented or issued credential characteristics w3c-fedid/digital-credentials#302, by @npdoty.
-
Establish a common classification of credential types used in this API w3c-fedid/digital-credentials#299, by @kdenhartog.
-
Choice of issuers and consequent exclusion risk w3c-fedid/digital-credentials#298, by @martinthomson.
-
Privacy Considerations: Consider incorporating information entropy when discussing linkable information w3c-fedid/digital-credentials#297, by @johannhof.
-
proof of authentication w3c-fedid/digital-credentials#296, by @nadalin.
-
Privacy Considerations: Possibly distinguish between 3P attested and self attested and identity / non-identity based w3c-fedid/digital-credentials#295, by @johannhof.
-
Exchanges user agency for greater compliance and convenience w3c-fedid/digital-credentials#293, by @kdenhartog.
-
Increased restriction of the ability to publish, view, and participate on the Web, and corresponding fragmentation of the Web as a whole w3c-fedid/digital-credentials#292, by @kdenhartog.
-
Prevent increased centralization of trust via strict Verifier requirements when presenting a credential w3c-fedid/digital-credentials#291, by @kdenhartog.
-
define consent and permission; explain split roles regarding consent w3c-fedid/digital-credentials#290, by @npdoty.
-
note designed-for-purpose alternatives and the risk of crowding out those options w3c-fedid/digital-credentials#289, by @npdoty.
-
user agents should limit to protocols listed in the registry that meet the group's requirements w3c-fedid/digital-credentials#288, by @npdoty.
-
Privacy Considerations for multiple presentation requests (and responses) w3c-fedid/digital-credentials#286, by @johannhof.
-
Editorial: Add references to definitions in the privacy considerations w3c-fedid/digital-credentials#284, by @johannhof.
-
User agents that only support authorized verifiers (for government credentials) w3c-fedid/digital-credentials#281, by @johannhof.
-
Can we require protocols to support unlinkable revocation? w3c-fedid/digital-credentials#280, by @johannhof.
-
Linkability and issuer involvement as a protocol requirement w3c-fedid/digital-credentials#279, by @johannhof.
-
Explain design choices for this API vs. alternatives w3c-fedid/digital-credentials#275, by @johannhof.
-
Security Considerations section w3c-fedid/digital-credentials#274, by @simoneonofri.
-
Security Considerations: Assumptions (System Layer and Network Layer) w3c-fedid/digital-credentials#273, by @simoneonofri.
-
protocol identifier is undefined w3c-fedid/digital-credentials#270, by @marcoscaceres.
-
Security/Privacy Considerations: Trust boundaries between the Wallet and the Browser? w3c-fedid/digital-credentials#269, by @simoneonofri.
-
friction and frequency minimization w3c-fedid/digital-credentials#268, by @npdoty.
-
reporting abuse of credential requests w3c-fedid/digital-credentials#267, by @npdoty.
-
registration of and commitment to a particular use case and purpose w3c-fedid/digital-credentials#266, by @npdoty.
-
voluntary usage and protections against coercion w3c-fedid/digital-credentials#265, by @npdoty.
-
Clarify the relationship and trust model of multiple user agents w3c-fedid/digital-credentials#263, by @johannhof.
-
Protocol registry: specification availability w3c-fedid/digital-credentials#257, by @martinthomson.
-
Protocol registry: royalty free requirement w3c-fedid/digital-credentials#256, by @martinthomson.
-
Define concrete privacy and security requirements for the supported protocols w3c-fedid/digital-credentials#255, by @martinthomson.
-
Should we normatively define elements of a permission prompt? w3c-fedid/digital-credentials#252, by @johannhof.
-
-
12 issues closed.
-
Write privacy considerations w3c-fedid/digital-credentials#183.
-
Establish a common classification of credential types used in this API w3c-fedid/digital-credentials#299.
-
Add a means for developers to check protocols allowed by user agents w3c-fedid/digital-credentials#219.
-
Explain design choices for this API vs. alternatives w3c-fedid/digital-credentials#275.
-
Increased restriction of the ability to publish, view, and participate on the Web, and corresponding fragmentation of the Web as a whole w3c-fedid/digital-credentials#292.
-
protocol identifier is undefined w3c-fedid/digital-credentials#270.
-
Privacy Considerations: Ensuring user choice over wallet involvement (avoid wallet surveillance) w3c-fedid/digital-credentials#247.
-
Privacy Considerations: User permission and transparency w3c-fedid/digital-credentials#244.
-
Scope of Privacy Considerations w3c-fedid/digital-credentials#241.
-
Explainer: no mention of what security and privacy properties of a request are desireable w3c-fedid/digital-credentials#108.
-
[Discuss] Abuse preventions and mitigations w3c-fedid/digital-credentials#30.
-
s/user consent/user permission w3c-fedid/digital-credentials#239.
-
-
38 issues received 100 new comments.
-
w3c-fedid/digital-credentials#35 (18 comments by @c2bo, @DemiMarie, @johannhof, @kdenhartog, @timcappalli)
-
reporting abuse of credential requests w3c-fedid/digital-credentials#267 (9 comments by @c2bo, @johannhof, @jyasskin, @npdoty, @simoneonofri, @timcappalli)
-
User agents that only support authorized verifiers (for government credentials) w3c-fedid/digital-credentials#281 (6 comments by @johannhof, @RByers, @timcappalli, @zoracon)
-
Can we require protocols to support unlinkable revocation? w3c-fedid/digital-credentials#280 (6 comments by @andrea-dintino, @c2bo, @jaromil, @johannhof, @simoneonofri)
-
user agents should limit to protocols listed in the registry that meet the group's requirements w3c-fedid/digital-credentials#288 (5 comments by @martinthomson, @npdoty, @timcappalli)
-
note designed-for-purpose alternatives and the risk of crowding out those options w3c-fedid/digital-credentials#289 (4 comments by @martinthomson, @RByers, @timcappalli)
-
Privacy review of the supported presentation protocols w3c-fedid/digital-credentials#226 (4 comments by @johannhof, @npdoty, @wseltzer)
-
Define concrete privacy and security requirements for the supported protocols w3c-fedid/digital-credentials#255 (4 comments by @johannhof, @npdoty, @simoneonofri)
-
Write privacy considerations w3c-fedid/digital-credentials#183 (3 comments by @johannhof, @npdoty, @wseltzer)
-
Add ISO/IEC 18013-7 Annex C to protocol registry w3c-fedid/digital-credentials#213 (3 comments by @marcoscaceres, @nadalin)
-
Consider requiring mitigation of script injection attacks. w3c-fedid/digital-credentials#133 (3 comments by @johannhof, @npdoty, @simoneonofri)
-
Handling Multiple Credentials from Different Wallets in DC API Presentation Responses w3c-fedid/digital-credentials#222 (3 comments by @c2bo, @npdoty, @TallTed)
-
Privacy Considerations: Consider incorporating information entropy when discussing linkable information w3c-fedid/digital-credentials#297 (2 comments by @johannhof, @martinthomson)
-
Prevent increased centralization of trust via strict Verifier requirements when presenting a credential w3c-fedid/digital-credentials#291 (2 comments by @kdenhartog, @npdoty)
-
Exchanges user agency for greater compliance and convenience w3c-fedid/digital-credentials#293 (2 comments by @kdenhartog, @npdoty)
-
Increased restriction of the ability to publish, view, and participate on the Web, and corresponding fragmentation of the Web as a whole w3c-fedid/digital-credentials#292 (2 comments by @kdenhartog, @npdoty)
-
Security Considerations section w3c-fedid/digital-credentials#274 (2 comments by @npdoty, @simoneonofri)
-
friction and frequency minimization w3c-fedid/digital-credentials#268 (2 comments by @johannhof, @simoneonofri)
-
Privacy Considerations: Possibly distinguish between 3P attested and self attested and identity / non-identity based w3c-fedid/digital-credentials#295 (1 comment by @kdenhartog)
-
Establish a common classification of credential types used in this API w3c-fedid/digital-credentials#299 (1 comment by @kdenhartog)
-
Add a means for developers to check protocols allowed by user agents w3c-fedid/digital-credentials#219 (1 comment by @johannhof)
-
Choice of issuers and consequent exclusion risk w3c-fedid/digital-credentials#298 (1 comment by @npdoty)
-
Privacy Considerations: Ensuring user choice over wallet involvement (avoid wallet surveillance) w3c-fedid/digital-credentials#247 (1 comment by @johannhof)
-
Privacy Considerations: User permission and transparency w3c-fedid/digital-credentials#244 (1 comment by @johannhof)
-
Explainer: no mention of what security and privacy properties of a request are desireable w3c-fedid/digital-credentials#108 (1 comment by @johannhof)
-
Privacy: ensuring RPs blinded to credential existence w3c-fedid/digital-credentials#105 (1 comment by @johannhof)
-
w3c-fedid/digital-credentials#30 (1 comment by @johannhof)
-
Security/Privacy Considerations: Trust boundaries between the Wallet and the Browser? w3c-fedid/digital-credentials#269 (1 comment by @timcappalli)
-
Explain design choices for this API vs. alternatives w3c-fedid/digital-credentials#275 (1 comment by @simoneonofri)
-
registration of and commitment to a particular use case and purpose w3c-fedid/digital-credentials#266 (1 comment by @johannhof)
-
voluntary usage and protections against coercion w3c-fedid/digital-credentials#265 (1 comment by @johannhof)
-
Privacy Considerations: "Spectrum of Privacy" w3c-fedid/digital-credentials#242 (1 comment by @npdoty)
-
w3c-fedid/digital-credentials#38 (1 comment by @PatStLouis)
-
Privacy Considerations: Preventing information leakage and fingerprinting w3c-fedid/digital-credentials#245 (1 comment by @simoneonofri)
-
-
18 pull requests opened.
-
Define interaction between platform credential chooser and the user agent w3c-fedid/digital-credentials#306, by @marcoscaceres.
-
Editorial: add API section w3c-fedid/digital-credentials#304, by @marcoscaceres.
-
chore: add Editor IDs w3c-fedid/digital-credentials#301, by @simoneonofri.
-
Chore: fix HTML Validator issues w3c-fedid/digital-credentials#300, by @simoneonofri.
-
Add additional issues to privacy considerations w3c-fedid/digital-credentials#287, by @johannhof.
-
Clean up privacy considerations TODO sections w3c-fedid/digital-credentials#285, by @johannhof.
-
Add initial privacy considerations for fingerprinting and data leakage w3c-fedid/digital-credentials#283, by @johannhof.
-
Add design considerations section to privacy considerations (fixes #275) w3c-fedid/digital-credentials#278, by @johannhof.
-
Security Considerations: Writing first round of threats and mitigatio… w3c-fedid/digital-credentials#277, by @simoneonofri.
-
Formally define 'protocol identifier' w3c-fedid/digital-credentials#276, by @marcoscaceres.
-
Security Considerations: Writing Introduction w3c-fedid/digital-credentials#272, by @simoneonofri.
-
Adds additional terminology w3c-fedid/digital-credentials#271, by @timcappalli.
-
Write initial privacy considerations for unnecessary use w3c-fedid/digital-credentials#262, by @johannhof.
-
Fix discovery typo w3c-fedid/digital-credentials#261, by @johannhof.
-
Add initial privacy considerations section for protocol requirements w3c-fedid/digital-credentials#260, by @johannhof.
-
Protocol registry: edited the group for seucrity reviews w3c-fedid/digital-credentials#258, by @simoneonofri.
-
Editorial: Make Tidy happy w3c-fedid/digital-credentials#254, by @johannhof.
-
Add initial text for permission & transparency w3c-fedid/digital-credentials#253, by @johannhof.
-
-
16 pull requests merged.
-
Add initial privacy considerations for fingerprinting and data leakage w3c-fedid/digital-credentials#283.
-
Chore: fix HTML Validator issues w3c-fedid/digital-credentials#300.
-
chore: add Editor IDs w3c-fedid/digital-credentials#301.
-
Write initial privacy considerations for unnecessary use w3c-fedid/digital-credentials#262.
-
Add userAgentAllowsProtocol static method w3c-fedid/digital-credentials#221.
-
Add design considerations section to privacy considerations (fixes #275) w3c-fedid/digital-credentials#278.
-
Formally define 'protocol identifier' w3c-fedid/digital-credentials#276.
-
Clean up privacy considerations TODO sections w3c-fedid/digital-credentials#285.
-
Add additional issues to privacy considerations w3c-fedid/digital-credentials#287.
-
Add initial privacy considerations section for protocol requirements w3c-fedid/digital-credentials#260.
-
Add initial text for permission & transparency w3c-fedid/digital-credentials#253.
-
Fix discovery typo w3c-fedid/digital-credentials#261.
-
Protocol registry: edited the group for seucrity reviews w3c-fedid/digital-credentials#258.
-
Editorial: Make Tidy happy w3c-fedid/digital-credentials#254.
-
Privacy Considerations: Add initial Introduction, Spectrum of Privacy sections w3c-fedid/digital-credentials#251.
-
s/user consent/user permission w3c-fedid/digital-credentials#248.
-
-
1 pull request closed.
-
Adds additional terminology w3c-fedid/digital-credentials#271.
-
-
24 pull requests received 526 new comments.
-
Write initial privacy considerations for unnecessary use w3c-fedid/digital-credentials#262 (171 comments by @burdges, @johannhof, @kdenhartog, @marcoscaceres, @mohamedamir, @npdoty, @RByers, @simoneonofri, @TallTed, @timcappalli)
-
Add initial text for permission & transparency w3c-fedid/digital-credentials#253 (63 comments by @c2bo, @johannhof, @mohamedamir, @npdoty, @RByers, @TallTed)
-
Add design considerations section to privacy considerations (fixes #275) w3c-fedid/digital-credentials#278 (50 comments by @johannhof, @marcoscaceres, @martinthomson, @npdoty)
-
Add initial privacy considerations for fingerprinting and data leakage w3c-fedid/digital-credentials#283 (47 comments by @johannhof, @marcoscaceres, @mohamedamir, @npdoty, @simoneonofri)
-
Add userAgentAllowsProtocol static method w3c-fedid/digital-credentials#221 (47 comments by @hlflanagan, @johannhof, @marcoscaceres, @MasterKale, @mohamedamir, @npdoty, @timcappalli, @wseltzer)
-
Add initial privacy considerations section for protocol requirements w3c-fedid/digital-credentials#260 (40 comments by @johannhof, @martinthomson, @mohamedamir, @npdoty, @RByers, @simoneonofri)
-
Privacy Considerations: Add initial Introduction, Spectrum of Privacy sections w3c-fedid/digital-credentials#251 (31 comments by @johannhof, @mohamedamir, @npdoty, @simoneonofri, @wseltzer)
-
Security Considerations: Writing Introduction w3c-fedid/digital-credentials#272 (16 comments by @marcoscaceres, @simoneonofri, @timcappalli)
-
Security Considerations: Writing first round of threats and mitigatio… w3c-fedid/digital-credentials#277 (13 comments by @marcoscaceres, @npdoty, @simoneonofri)
-
Formally define 'protocol identifier' w3c-fedid/digital-credentials#276 (10 comments by @marcoscaceres, @mohamedamir)
-
Adds additional terminology w3c-fedid/digital-credentials#271 (7 comments by @hlflanagan, @marcoscaceres, @MasterKale, @timcappalli)
-
Add guidance on how to handle multiple presentation request entries w3c-fedid/digital-credentials#249 (6 comments by @marcoscaceres, @MasterKale, @TallTed, @wseltzer)
-
Editorial: add API section w3c-fedid/digital-credentials#304 (4 comments by @marcoscaceres, @TallTed)
-
Add additional issues to privacy considerations w3c-fedid/digital-credentials#287 (4 comments by @johannhof, @marcoscaceres)
-
Add a11y guidance for user agents w3c-fedid/digital-credentials#238 (3 comments by @marcoscaceres, @wseltzer)
-
Require JSON serialization checks coming in w3c-fedid/digital-credentials#179 (2 comments by @marcoscaceres, @mohamedamir)
-
Define interaction between platform credential chooser and the user agent w3c-fedid/digital-credentials#306 (1 comment by @TallTed)
-
w3c-fedid/digital-credentials#282 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#259 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#250 (1 comment by @w3cbot)
-
w3c-fedid/FedCM
-
10 issues opened.
-
Wrong Web IDL type for URLs in Federated Credential Management API w3c-fedid/FedCM#754, by @dontcallmedom-bot.
-
IDP section is non-normative and out of date w3c-fedid/FedCM#753, by @mooreds.
-
Inconsistency between `getUserInfo` and UI hints from `IdentityProviderAccount` w3c-fedid/FedCM#750, by @bvandersloot-mozilla.
-
Architecture (TAG) review w3c-fedid/FedCM#749, by @wseltzer.
-
Potential issue with Clear-Site-Data and unknown login status w3c-fedid/FedCM#746, by @npm1.
-
Add status checks to fetches w3c-fedid/FedCM#745, by @npm1.
-
`IdentityProvider.resolve()` idl doesn't show a returned `Promise` in the IDL w3c-fedid/FedCM#742, by @bvandersloot-mozilla.
-
Accessibility review w3c-fedid/FedCM#741, by @wseltzer.
-
Opened in error w3c-fedid/FedCM#740, by @wseltzer.
-
Assert in step 7.12 of the Create Identity credential algorithm can fail w3c-fedid/FedCM#734, by @togamid.
-
-
6 issues closed.
-
Assert in step 7.12 of the Create Identity credential algorithm can fail w3c-fedid/FedCM#734.
-
Users may be confused after showing intent to sign in but the sign-in is failed w3c-fedid/FedCM#488.
-
`IdentityProvider.resolve()` idl doesn't show a returned `Promise` in the IDL w3c-fedid/FedCM#742.
-
Opened in error w3c-fedid/FedCM#740.
-
Fields `name` and `given_name` have unclear usage w3c-fedid/FedCM#680.
-
-
12 issues received 32 new comments.
-
Tracking through IDP with individualized account and client_metadata endpoints w3c-fedid/FedCM#700 (9 comments by @bvandersloot-mozilla, @hlflanagan, @npm1, @samuelgoto, @togamid)
-
Assert in step 7.12 of the Create Identity credential algorithm can fail w3c-fedid/FedCM#734 (5 comments by @cbiesinger, @npm1, @togamid)
-
Support showing iframe origins in the UI, when they are third-party w3c-fedid/FedCM#725 (4 comments by @bvandersloot-mozilla, @hlflanagan, @yi-gu)
-
Inconsistency between `getUserInfo` and UI hints from `IdentityProviderAccount` w3c-fedid/FedCM#750 (3 comments by @bvandersloot-mozilla, @cbiesinger, @TallTed)
-
w3c-fedid/FedCM#471 (1 comment by @mooreds)
-
`IdentityProvider.resolve()` idl doesn't show a returned `Promise` in the IDL w3c-fedid/FedCM#742 (1 comment by @npm1)
-
Support chained authentication flows before reducing heuristics and classifications/lists in navigational tracking mitigations w3c-fedid/FedCM#618 (1 comment by @mooreds)
-
-
11 pull requests opened.
-
Document the webdriver command to use another account. w3c-fedid/FedCM#752, by @cbiesinger.
-
Fix some promise issues in getUserInfo w3c-fedid/FedCM#751, by @npm1.
-
s/triples/quadruples w3c-fedid/FedCM#748, by @npm1.
-
Fix typo with resolve w3c-fedid/FedCM#744, by @npm1.
-
Make resolve return a Promise w3c-fedid/FedCM#743, by @npm1.
-
Corrected the link at Step 4 w3c-fedid/FedCM#739, by @pottis.
-
Inspecting FedCM API network requests within DevTools w3c-fedid/FedCM#738, by @pottis.
-
Fix spec bugs reported by togamid w3c-fedid/FedCM#737, by @npm1.
-
Add explainer on FedCM using devtools w3c-fedid/FedCM#736, by @pottis.
-
Update README.md w3c-fedid/FedCM#733, by @npm1.
-
Make connected accounts set a quadruple w3c-fedid/FedCM#732, by @npm1.
-
-
13 pull requests merged.
-
Fix spec bugs reported by togamid w3c-fedid/FedCM#737.
-
Add API to show error messages from failed token fetches w3c-fedid/FedCM#498.
-
Fix some promise issues in getUserInfo w3c-fedid/FedCM#751.
-
s/triples/quadruples w3c-fedid/FedCM#748.
-
Specify "Use another account". w3c-fedid/FedCM#678.
-
Make connected accounts set a quadruple w3c-fedid/FedCM#732.
-
Fix typo with resolve w3c-fedid/FedCM#744.
-
Make resolve return a Promise w3c-fedid/FedCM#743.
-
Corrected the link at Step 4 w3c-fedid/FedCM#739.
-
Inspecting FedCM API network requests within DevTools w3c-fedid/FedCM#738.
-
State that resolve() does nothing outside of continue_on w3c-fedid/FedCM#717.
-
Update README.md w3c-fedid/FedCM#733.
-
Clarify that given_name and name are not to be composed w3c-fedid/FedCM#731.
-
-
1 pull request closed.
-
Add explainer on FedCM using devtools w3c-fedid/FedCM#736.
-
-
1 pull request reopened.
-
Inspecting FedCM API network requests within DevTools w3c-fedid/FedCM#738, by @pottis.
-
-
12 pull requests received 115 new comments.
-
Fix spec bugs reported by togamid w3c-fedid/FedCM#737 (22 comments by @hlflanagan, @npm1, @TallTed, @togamid)
-
Specify "Use another account". w3c-fedid/FedCM#678 (10 comments by @bvandersloot-mozilla, @cbiesinger, @npm1)
-
Make connected accounts set a quadruple w3c-fedid/FedCM#732 (7 comments by @bvandersloot-mozilla, @mooreds, @npm1, @TallTed, @wseltzer)
-
Inspecting FedCM API network requests within DevTools w3c-fedid/FedCM#738 (4 comments by @npm1, @pottis)
-
Document the webdriver command to use another account. w3c-fedid/FedCM#752 (3 comments by @cbiesinger, @npm1)
-
Clarify that given_name and name are not to be composed w3c-fedid/FedCM#731 (1 comment by @samuelgoto)
Past meetings
-
6 meetings.
Participants
-
3 participants joined.
-
Alan Wang (Mastercard Incorporated) joined.
-
Ryan Galluzzo (National Institute of Standards and Technology (NIST)) joined.
-
Tomasz Blachowicz (Mastercard Incorporated) joined.
-
-
1 organization joined.
-
Mastercard Incorporated joined.
-
GitHub
w3c-fedid/FedCM
-
5 issues opened.
-
Support showing iframe origins in the UI, when they are third-party w3c-fedid/FedCM#725, by @cbiesinger.
-
4 issues closed.
-
Use cases for Cross-Site Cookie Access through Storage Access API after FedCM grant? w3c-fedid/FedCM#467.
-
Allow IDPs to use multiple config files within an eTLD+1 w3c-fedid/FedCM#552.
-
Allowing IDPs to expose different account lists in different contexts w3c-fedid/FedCM#553.
-
Runner seems broken w3c-fedid/FedCM#721.
-
-
9 issues received 20 new comments.
-
`globalObject`s should be the top level window, rather than the cross site iframe when Permissions Policy is used w3c-fedid/FedCM#729 (9 comments by @bvandersloot-mozilla, @cbiesinger, @gffletch, @wseltzer)
-
Support chained authentication flows before reducing heuristics and classifications/lists in navigational tracking mitigations w3c-fedid/FedCM#618 (3 comments by @npm1, @philsmart)
-
w3c-fedid/FedCM#467 (1 comment by @npm1)
-
Allowing IDPs to expose different account lists in different contexts w3c-fedid/FedCM#553 (1 comment by @npm1)
-
Support showing iframe origins in the UI, when they are third-party w3c-fedid/FedCM#725 (1 comment by @hlflanagan)
-
FedCM "core": move "extensions" out of the current spec into an independent spec w3c-fedid/FedCM#703 (1 comment by @wseltzer)
-
-
3 pull requests opened.
-
Clarify that given_name and name are not to be composed w3c-fedid/FedCM#731, by @npm1.
-
Update build-idl.yaml w3c-fedid/FedCM#724, by @npm1.
-
Do not set request's window w3c-fedid/FedCM#723, by @domenic.
-
-
2 pull requests merged.
-
Update build-idl.yaml w3c-fedid/FedCM#724.
-
Do not set request's window w3c-fedid/FedCM#723.
-
w3c-fedid/digital-credentials
-
14 issues opened.
-
Privacy Considerations: Ensuring user choice over wallet involvement (avoid wallet surveillance) w3c-fedid/digital-credentials#247, by @johannhof.
-
Privacy Considerations: Types of Wallets and trust in different Wallets w3c-fedid/digital-credentials#246, by @johannhof.
-
Privacy Considerations: Preventing information leakage and fingerprinting w3c-fedid/digital-credentials#245, by @johannhof.
-
Privacy Considerations: User permission and transparency w3c-fedid/digital-credentials#244, by @johannhof.
-
Privacy Considerations: Addressing "unnecessary" usage of the API w3c-fedid/digital-credentials#243, by @johannhof.
-
Privacy Considerations: "Spectrum of Privacy" w3c-fedid/digital-credentials#242, by @johannhof.
-
Scope of Privacy Considerations w3c-fedid/digital-credentials#241, by @johannhof.
-
Registry requirements should not use RFC2119 language w3c-fedid/digital-credentials#240, by @marcoscaceres.
-
s/user consent/user permission w3c-fedid/digital-credentials#239, by @timcappalli.
-
Horizontal Review - Security w3c-fedid/digital-credentials#233, by @MasterKale.
-
Horizontal Review - Privacy w3c-fedid/digital-credentials#232, by @MasterKale.
-
Horizontal Review - Internationalization w3c-fedid/digital-credentials#231, by @MasterKale.
-
Horizontal Review - Architecture w3c-fedid/digital-credentials#230, by @MasterKale.
-
Horizontal Review - Accessibility w3c-fedid/digital-credentials#229, by @MasterKale.
-
-
2 issues closed.
-
Whats the capability negotiation model assumed between the relying party (RP) / origin and the wallet / provider? w3c-fedid/digital-credentials#76.
-
Support for issuance w3c-fedid/digital-credentials#167.
-
-
17 issues received 40 new comments.
-
Write privacy considerations w3c-fedid/digital-credentials#183 (9 comments by @johannhof, @npdoty, @wseltzer)
-
Scope of Privacy Considerations w3c-fedid/digital-credentials#241 (4 comments by @johannhof, @npdoty, @simoneonofri)
-
[Registry] Re-evaluate "freely available" requirement w3c-fedid/digital-credentials#214 (4 comments by @hober, @npdoty, @plehegar)
-
Registry requirements should not use RFC2119 language w3c-fedid/digital-credentials#240 (3 comments by @hober, @npdoty, @timcappalli)
-
Privacy Considerations: Addressing "unnecessary" usage of the API w3c-fedid/digital-credentials#243 (3 comments by @johannhof, @simoneonofri)
-
Privacy Considerations: Types of Wallets and trust in different Wallets w3c-fedid/digital-credentials#246 (2 comments by @npdoty, @simoneonofri)
-
Privacy Considerations: User permission and transparency w3c-fedid/digital-credentials#244 (2 comments by @johannhof)
-
Horizontal Review Preparation: DC API w3c-fedid/digital-credentials#227 (2 comments by @MasterKale, @wseltzer)
-
w3c-fedid/digital-credentials#38 (1 comment by @gp-iaik)
-
w3c-fedid/digital-credentials#76 (1 comment by @tplooker)
-
Handling Multiple Credentials from Different Wallets in DC API Presentation Responses w3c-fedid/digital-credentials#222 (1 comment by @TimoGlastra)
-
Add a means for developers to check protocols allowed by user agents w3c-fedid/digital-credentials#219 (1 comment by @npdoty)
-
w3c-fedid/digital-credentials#35 (1 comment by @DemiMarie)
-
-
8 pull requests opened.
-
Privacy Considerations: Add initial Introduction, Spectrum of Privacy sections w3c-fedid/digital-credentials#251, by @johannhof.
-
Add guidance on how to handle multiple presentation request entries w3c-fedid/digital-credentials#249, by @MasterKale.
-
s/user consent/user permission w3c-fedid/digital-credentials#248, by @timcappalli.
-
Add a11y guidance for user agents w3c-fedid/digital-credentials#238, by @MasterKale.
-
Remove registry inclusion issue w3c-fedid/digital-credentials#237, by @mohamedamir.
-
Editoral: Link to registry inclusion criteria definitions w3c-fedid/digital-credentials#236, by @mohamedamir.
-
Editorial: Fix links to request field to use the new format in the register inclusion criteria w3c-fedid/digital-credentials#235, by @mohamedamir.
-
Switch goto@google.com for mamir@google.com to edit Digital Credentials w3c-fedid/digital-credentials#234, by @samuelgoto.
-
-
5 pull requests merged.
-
Editoral: Link to registry inclusion criteria definitions w3c-fedid/digital-credentials#236.
-
Editorial: Fix links to request field to use the new format in the register inclusion criteria w3c-fedid/digital-credentials#235.
-
Remove registry inclusion issue w3c-fedid/digital-credentials#237.
-
Switch goto@google.com for mamir@google.com to edit Digital Credentials w3c-fedid/digital-credentials#234.
-
Include Digital Credential Issuance in the Spec w3c-fedid/digital-credentials#204.
-
-
7 pull requests received 33 new comments.
-
Add userAgentAllowsProtocol static method w3c-fedid/digital-credentials#221 (15 comments by @MasterKale, @npdoty, @timcappalli)
-
Editoral: Link to registry inclusion criteria definitions w3c-fedid/digital-credentials#236 (8 comments by @mohamedamir, @TallTed, @timcappalli)
-
Editorial: Fix links to request field to use the new format in the register inclusion criteria w3c-fedid/digital-credentials#235 (3 comments by @TallTed)
-
Switch goto@google.com for mamir@google.com to edit Digital Credentials w3c-fedid/digital-credentials#234 (3 comments by @samuelgoto, @timcappalli, @wseltzer)
-
Remove registry inclusion issue w3c-fedid/digital-credentials#237 (2 comments by @marcoscaceres, @mohamedamir)
-
w3c-fedid/digital-credentials#228 (1 comment by @w3cbot)
-
Past meetings
Participants
-
9 participants joined.
-
Anthony Nadalin (W3C Invited Experts) joined.
-
Lee Campbell (Google LLC) joined.
-
Christian Bormann (SPRIND GmbH) joined.
-
Oliver Terbu (Mattr Limited) joined.
-
Tobias Looker (Mattr Limited) joined.
-
Torsten Lodderstedt (SPRIND GmbH) joined.
-
Kristina Yasuda (SPRIND GmbH) joined.
-
Christian Rask (1Password) joined.
-
Albert Schibani (Capital One Discover Network) joined.
-
-
10 participants left.
-
Duy-Tung LUU (CANTON CONSULTING) left.
-
Joshua Thomas (Ignite Retail Technology) left.
-
Zane Durkin (Ignite Retail Technology) left.
-
Brian McManus (Ignite Retail Technology) left.
-
Tobias Wegmann (The German Association for the Digital Economy (BVDW)) left.
-
Michael Jones (Mattr Limited) left.
-
Anthony Nadalin (W3C Invited Experts) left.
-
Nakjo Shishkov (Netcetera) left.
-
Oliver Terbu (Mattr Limited) left.
-
Tobias Looker (Mattr Limited) left.
-
-
4 organizations joined.
-
Mattr Limited joined.
-
SPRIND GmbH joined.
-
Ping Identity joined.
-
1Password joined.
-
GitHub
w3c-fedid/digital-credentials
-
8 issues opened.
-
Horizontal Review Preparation: DC API w3c-fedid/digital-credentials#227, by @wseltzer.
-
Privacy review of the supported presentation protocols w3c-fedid/digital-credentials#226, by @npdoty.
-
Create an issue template for registration w3c-fedid/digital-credentials#223, by @marcoscaceres.
-
Handling Multiple Credentials from Different Wallets in DC API Presentation Responses w3c-fedid/digital-credentials#222, by @mohamedamir.
-
Support for multiple requests in a get call w3c-fedid/digital-credentials#220, by @MasterKale.
-
Add a means for developers to check protocols allowed by user agents w3c-fedid/digital-credentials#219, by @timcappalli.
-
Document WG security review requirements for protocols w3c-fedid/digital-credentials#215, by @timcappalli.
-
[Registry] Re-evaluate "freely available" requirement w3c-fedid/digital-credentials#214, by @timcappalli.
-
-
6 issues closed.
-
Top level request object structure should be fully defined by protocol identifier w3c-fedid/digital-credentials#185.
-
[spec] add statement about responses with PII MUST be encrypted w3c-fedid/digital-credentials#124.
-
Registry inclusion criteria w3c-fedid/digital-credentials#58.
-
What are the protocol identifier naming rules? w3c-fedid/digital-credentials#191.
-
Intent to Migrate: Digital Credentials w3c-fedid/digital-credentials#205.
-
WICG Digital Credentials group consensus to move work w3c-fedid/digital-credentials#206.
-
-
1 issue reopened.
-
Intent to Migrate: Digital Credentials w3c-fedid/digital-credentials#205, by @marcoscaceres.
-
-
11 issues received 27 new comments.
-
Intent to Migrate: Digital Credentials w3c-fedid/digital-credentials#205 (9 comments by @hlflanagan, @marcoscaceres, @simoneonofri, @timcappalli)
-
Add getClientCapabilities method for feature detection w3c-fedid/digital-credentials#200 (4 comments by @MasterKale, @npdoty, @timcappalli)
-
Add a means for developers to check protocols allowed by user agents w3c-fedid/digital-credentials#219 (3 comments by @hlflanagan, @MasterKale)
-
Handling Multiple Credentials from Different Wallets in DC API Presentation Responses w3c-fedid/digital-credentials#222 (2 comments by @hlflanagan, @npdoty)
-
Support for multiple requests in a get call w3c-fedid/digital-credentials#220 (2 comments by @hlflanagan, @MasterKale)
-
[Registry] Re-evaluate "freely available" requirement w3c-fedid/digital-credentials#214 (2 comments by @bc-pi, @plehegar)
-
Add a way to check what protocols are supported w3c-fedid/digital-credentials#168 (1 comment by @MasterKale)
-
Top level request object structure should be fully defined by protocol identifier w3c-fedid/digital-credentials#185 (1 comment by @timcappalli)
-
w3c-fedid/digital-credentials#58 (1 comment by @marcoscaceres)
-
WICG Digital Credentials group consensus to move work w3c-fedid/digital-credentials#206 (1 comment by @timcappalli)
-
Add OpenID for Verifiable Presentations (OpenID4VP) to registry w3c-fedid/digital-credentials#211 (1 comment by @bc-pi)
-
-
5 pull requests opened.
-
Fix spec link in explainer.md w3c-fedid/digital-credentials#225, by @RByers.
-
Add userAgentAllowsProtocol static method w3c-fedid/digital-credentials#221, by @timcappalli.
-
Update README.md with WG w3c-fedid/digital-credentials#218, by @wseltzer.
-
Update Respec config with WG details w3c-fedid/digital-credentials#217, by @timcappalli.
-
Update CONTRIBUTING.md w3c-fedid/digital-credentials#216, by @wseltzer.
-
-
5 pull requests merged.
-
Fix spec link in explainer.md w3c-fedid/digital-credentials#225.
-
Define registry inclusion rules w3c-fedid/digital-credentials#157.
-
Update Respec config with WG details w3c-fedid/digital-credentials#217.
-
Update README.md with WG w3c-fedid/digital-credentials#218.
-
Update CONTRIBUTING.md w3c-fedid/digital-credentials#216.
-
-
6 pull requests received 61 new comments.
-
Define registry inclusion rules w3c-fedid/digital-credentials#157 (41 comments by @bc-pi, @c2bo, @jogu, @marcoscaceres, @MasterKale, @npdoty, @RByers, @Sakurann, @TallTed, @timcappalli, @TomCJones, @wseltzer)
-
Add userAgentAllowsProtocol static method w3c-fedid/digital-credentials#221 (10 comments by @c2bo, @marcoscaceres, @MasterKale, @RByers, @samuelgoto, @TallTed, @timcappalli)
-
Include Digital Credential Issuance in the Spec w3c-fedid/digital-credentials#204 (6 comments by @marcoscaceres, @timcappalli, @wseltzer)
-
Fix spec link in explainer.md w3c-fedid/digital-credentials#225 (2 comments by @RByers, @samuelgoto)
-
w3c-fedid/digital-credentials#224 (1 comment by @w3cbot)
-
w3c-fedid/FedCM
-
5 issues opened.
-
Decide on a format for phone numbers w3c-fedid/FedCM#722, by @cbiesinger.
-
Runner seems broken w3c-fedid/FedCM#721, by @npm1.
-
Enterprise Scenarios: admin consent for users w3c-fedid/FedCM#715, by @EmLauber.
-
Is the current the definition of "core" backwards incompatible? w3c-fedid/FedCM#714, by @samuelgoto.
-
Does "core" need to introduce feature detection for features in "extensions"? w3c-fedid/FedCM#713, by @samuelgoto.
-
-
5 issues closed.
-
Reconsider required email field in IdentityProviderAccount w3c-fedid/FedCM#435.
-
Allow selecting an account without email addresses w3c-fedid/FedCM#639.
-
Spec says we send SameSite=Strict cookies w3c-fedid/FedCM#609.
-
Why is the client_metadata_endpoint required in the config response? w3c-fedid/FedCM#701.
-
Why Sec-FedCM-CSRF and not Sec-Fetch-Mode w3c-fedid/FedCM#320.
-
-
16 issues received 44 new comments.
-
Decide on a format for phone numbers w3c-fedid/FedCM#722 (7 comments by @bhjelm-yubico, @cbiesinger, @TallTed)
-
Why must SameSite=none? w3c-fedid/FedCM#587 (6 comments by @anderspitman, @bc-pi, @hlflanagan, @npm1, @thhck)
-
Does "core" need to introduce feature detection for features in "extensions"? w3c-fedid/FedCM#713 (3 comments by @bvandersloot-mozilla, @hlflanagan, @timcappalli)
-
Enterprise Scenarios: admin consent for users w3c-fedid/FedCM#715 (3 comments by @halflumi, @hlflanagan, @johannhof)
-
Allow selecting an account without email addresses w3c-fedid/FedCM#639 (3 comments by @cbiesinger, @samuelgoto)
-
FedCM "core": move "extensions" out of the current spec into an independent spec w3c-fedid/FedCM#703 (2 comments by @hlflanagan, @npm1)
-
Augment autofill with a `conditional` get w3c-fedid/FedCM#694 (2 comments by @jyasskin, @samuelgoto)
-
Spec says we send SameSite=Strict cookies w3c-fedid/FedCM#609 (2 comments by @cbiesinger, @wseltzer)
-
Is the current the definition of "core" backwards incompatible? w3c-fedid/FedCM#714 (1 comment by @TallTed)
-
-
4 pull requests opened.
-
Add `tel` and `username` attributes w3c-fedid/FedCM#718, by @cbiesinger.
-
State that resolve() does nothing outside of continue_on w3c-fedid/FedCM#717, by @cbiesinger.
-
Make client metadata optional w3c-fedid/FedCM#716, by @npm1.
-
Move extension parts into issues in spec w3c-fedid/FedCM#712, by @npm1.
-
-
3 pull requests merged.
-
Add `tel` and `username` attributes w3c-fedid/FedCM#718.
-
Make client metadata optional w3c-fedid/FedCM#716.
-
Move extension parts into issues in spec w3c-fedid/FedCM#712.
-
-
5 pull requests received 53 new comments.
-
Set limit on size of `providers` w3c-fedid/FedCM#711 (19 comments by @bvandersloot-mozilla, @hlflanagan, @npm1, @TallTed)
-
Add `tel` and `username` attributes w3c-fedid/FedCM#718 (18 comments by @cbiesinger, @hlflanagan, @npm1, @TallTed)
-
Move extension parts into issues in spec w3c-fedid/FedCM#712 (8 comments by @bvandersloot-mozilla, @npm1, @TallTed)
-
State that resolve() does nothing outside of continue_on w3c-fedid/FedCM#717 (7 comments by @cbiesinger, @npm1, @samuelgoto, @TallTed)
-
w3c-fedid/Administration
-
1 pull request merged.
-
Editorial updates w3c-fedid/Administration#13.
-
-
1 pull request received 5 new comments.
Past meetings
Participants
-
12 participants joined.
-
Emily Lauber (Microsoft Corporation) joined.
-
Michael Jones (W3C Invited Experts) joined.
-
Ketan Mehta (National Institute of Standards and Technology (NIST)) joined.
-
ㅤ Pascoe (Apple Inc.) joined.
-
Yoav Weiss (Shopify) joined.
-
Ilya Grigorik (Shopify) joined.
-
Carl Prosack (Department of Homeland Security) joined.
-
Chris Fredrickson (Google LLC) joined.
-
Martin Thomson (Mozilla Foundation) joined.
-
Frank Somich (Google LLC) joined.
-
Erica Kovac (Google LLC) joined.
-
Johann Hofmann (Google LLC) joined.
-
-
1 participant left.
-
Carl Prosack (Department of Homeland Security) left.
-
-
16 organizations joined.
-
Yubico joined.
-
Microsoft Corporation joined.
-
Tradeverifyd joined.
-
OpenLink Software Inc. joined.
-
SURF bv joined.
-
Samsung Electronics Co., Ltd. joined.
-
National Institute of Standards and Technology (NIST) joined.
-
Apple Inc. joined.
-
Shopify joined.
-
OneSpan joined.
-
MITRE Corporation joined.
-
Inrupt Inc. joined.
-
Department of Homeland Security joined.
-
Visa joined.
-
Mozilla Foundation joined.
-
Google LLC joined.
-
GitHub
w3c-fedid/digital-credentials
-
9 issues opened.
-
Add ISO/IEC 18013-7 Annex C to protocol registry w3c-fedid/digital-credentials#213, by @Willewragtag.
-
Add OpenID for Verifiable Credential Issuance (OpenID4VCI) to registry w3c-fedid/digital-credentials#212, by @timcappalli.
-
Add OpenID for Verifiable Presentations (OpenID4VP) to registry w3c-fedid/digital-credentials#211, by @timcappalli.
-
Make `requests` member `required` for DigitalCredentialRequestOptions w3c-fedid/digital-credentials#210, by @marcoscaceres.
-
enumerated values for purpose, sharing and retention in API method w3c-fedid/digital-credentials#209, by @npdoty.
-
require in-context in-content explanation and an element for user-initiated presentation w3c-fedid/digital-credentials#208, by @npdoty.
-
Issuance: multiple requests w3c-fedid/digital-credentials#207, by @timcappalli.
-
WICG Digital Credentials group consensus to move work w3c-fedid/digital-credentials#206, by @timcappalli.
-
Intent to Migrate: Digital Credentials w3c-fedid/digital-credentials#205, by @marcoscaceres.
-
-
1 issue closed.
-
How much is really in common between different `IdentityCredential` types? w3c-fedid/digital-credentials#14.
-
-
9 issues received 26 new comments.
-
Intent to Migrate: Digital Credentials w3c-fedid/digital-credentials#205 (9 comments by @marcoscaceres, @npdoty, @simoneonofri, @timcappalli)
-
require in-context in-content explanation and an element for user-initiated presentation w3c-fedid/digital-credentials#208 (5 comments by @bvandersloot-mozilla, @marcoscaceres, @npdoty, @samuelgoto)
-
Add OpenID for Verifiable Presentations (OpenID4VP) to registry w3c-fedid/digital-credentials#211 (2 comments by @marcoscaceres, @MasterKale)
-
[spec] add statement about responses with PII MUST be encrypted w3c-fedid/digital-credentials#124 (1 comment by @timcappalli)
-
What are the protocol identifier naming rules? w3c-fedid/digital-credentials#191 (1 comment by @timcappalli)
-
Add ISO/IEC 18013-7 Annex C to protocol registry w3c-fedid/digital-credentials#213 (1 comment by @marcoscaceres)
-
[spec] DigitalCredentialRequestOptions and DigitalCredential objects must be JSON serializable w3c-fedid/digital-credentials#125 (1 comment by @MasterKale)
-
-
3 pull requests received 100 new comments.
-
Include Digital Credential Issuance in the Spec w3c-fedid/digital-credentials#204 (93 comments by @marcoscaceres, @mohamedamir, @samuelgoto, @TallTed, @timcappalli)
-
Define registry inclusion rules w3c-fedid/digital-credentials#157 (6 comments by @marcoscaceres, @timcappalli)
-
Require JSON serialization checks coming in w3c-fedid/digital-credentials#179 (1 comment by @marcoscaceres)
-
w3c-fedid/FedCM
-
3 issues opened.
-
How to test fedcm with frontend testing library like playwrite, cypress etc.. w3c-fedid/FedCM#705, by @thhck.
-
FedCM "core": break Web Platform tests between "core" and "extensions" w3c-fedid/FedCM#704, by @samuelgoto.
-
FedCM "core": move "extensions" out of the current spec into an independent spec w3c-fedid/FedCM#703, by @samuelgoto.
-
-
1 issue closed.
-
How to test fedcm with frontend testing library like playwrite, cypress etc.. w3c-fedid/FedCM#705.
-
-
7 issues received 23 new comments.
-
FedCM "core": move "extensions" out of the current spec into an independent spec w3c-fedid/FedCM#703 (9 comments by @bvandersloot-mozilla, @npm1, @samuelgoto, @selfissued, @TallTed, @wseltzer)
-
How to test fedcm with frontend testing library like playwrite, cypress etc.. w3c-fedid/FedCM#705 (3 comments by @cbiesinger, @samuelgoto, @thhck)
-
FedCM "core": break Web Platform tests between "core" and "extensions" w3c-fedid/FedCM#704 (1 comment by @wseltzer)
-
w3c-fedid/FedCM#317 (1 comment by @cbiesinger)
-
-
5 pull requests opened.
-
Set limit on size of `providers` w3c-fedid/FedCM#711, by @npm1.
-
Add login_url in section 3.2 ("The config file") w3c-fedid/FedCM#710, by @cbiesinger.
-
Update privacy & security questionnaire w3c-fedid/FedCM#708, by @npm1.
-
Disambiguate "allowed to use" w3c-fedid/FedCM#707, by @cbiesinger.
-
Fix bikeshed syntax error w3c-fedid/FedCM#706, by @cbiesinger.
-
-
6 pull requests merged.
-
Add login_url in section 3.2 ("The config file") w3c-fedid/FedCM#710.
-
Add single-get multi IDP support for passive mode w3c-fedid/FedCM#686.
-
Update privacy & security questionnaire w3c-fedid/FedCM#708.
-
Specify account labels w3c-fedid/FedCM#669.
-
Disambiguate "allowed to use" w3c-fedid/FedCM#707.
-
Fix bikeshed syntax error w3c-fedid/FedCM#706.
-
-
6 pull requests received 30 new comments.
-
Specify "Use another account". w3c-fedid/FedCM#678 (13 comments by @bvandersloot-mozilla, @cbiesinger, @npm1, @wseltzer)
-
Specify account labels w3c-fedid/FedCM#669 (9 comments by @bvandersloot-mozilla, @cbiesinger, @npm1, @wseltzer)
-
Add single-get multi IDP support for passive mode w3c-fedid/FedCM#686 (3 comments by @bvandersloot-mozilla, @npm1, @wseltzer)
-
Add login_url in section 3.2 ("The config file") w3c-fedid/FedCM#710 (2 comments by @cbiesinger, @npm1)
-
Specify the webdriver command to open terms of service and privacy po… w3c-fedid/FedCM#610 (2 comments by @TallTed)
-
w3c-fedid/Administration
-
1 pull request received 9 new comments.
-
Update proposals-CG-WG.md w3c-fedid/Administration#12 (9 comments by @elf-pavlik, @hlflanagan, @npm1)
-
Lifecycle
-
1 charter started.
-
Chartered until 25 February 2027. Participants had to rejoin under this charter.
-
Past meetings
Participants
-
3 participants joined.
-
Helen Qin (Google LLC) joined.
-
Anna Pobletts (1Password) joined.
-
Samuel Schlesinger (Google LLC) joined.
-
-
2 participants left.
-
Apoorva Deshpande (Okta) left.
-
George Fletcher (W3C Invited Experts) left.
-
-
6 organizations joined.
-
Okta joined.
-
Spherical Cow Consulting joined.
-
Capital One Discover Network joined.
-
Cisco joined.
-
Idura joined.
-
Center for Democracy and Technology joined.
-
-
29 organizations left.
-
1Password left.
-
Visa left.
-
MITRE Corporation left.
-
Capital One Discover Network left.
-
CANTON CONSULTING left.
-
Apple Inc. left.
-
Ignite Retail Technology left.
-
OneSpan left.
-
Shopify left.
-
Samsung Electronics Co., Ltd. left.
-
Idura left.
-
The German Association for the Digital Economy (BVDW) left.
-
Cisco left.
-
Microsoft Corporation left.
-
OpenLink Software Inc. left.
-
Netcetera left.
-
Mattr Limited left.
-
Inrupt Inc. left.
-
Google LLC left.
-
Mozilla Foundation left.
-
Ping Identity left.
-
Yubico left.
-
Department of Homeland Security left.
-
Alibaba Group left.
-
Tradeverifyd left.
-
SURF bv left.
-
Spherical Cow Consulting left.
-
Okta left.
-
Center for Democracy and Technology left.
-
GitHub
w3c-fedid/FedCM
-
7 issues opened.
-
Skip accounts_endpoint call when there's no chance of success w3c-fedid/FedCM#702, by @ekovac.
-
Why is the client_metadata_endpoint required in the config response? w3c-fedid/FedCM#701, by @togamid.
-
Tracking through IDP with individualized account and client_metadata endpoints w3c-fedid/FedCM#700, by @togamid.
-
If an RP page has an XSS risk, how can we avoid token leakage in the FedCM login process? w3c-fedid/FedCM#698, by @Yekongs.
-
login_url not documented in Section 3.2 w3c-fedid/FedCM#697, by @togamid.
-
Algorithm [=attempt to disconnect=] uses optional parameter as required w3c-fedid/FedCM#696, by @bvandersloot-mozilla.
-
Browser as an IdP w3c-fedid/FedCM#695, by @EAzari.
-
-
3 issues closed.
-
Algorithm [=attempt to disconnect=] uses optional parameter as required w3c-fedid/FedCM#696.
-
Browser as an IdP w3c-fedid/FedCM#695.
-
Security considerations should be consistently organised by security risk? w3c-fedid/FedCM#685.
-
-
14 issues received 61 new comments.
-
If an RP page has an XSS risk, how can we avoid token leakage in the FedCM login process? w3c-fedid/FedCM#698 (18 comments by @aaronpk, @johannhof, @philsmart, @samuelgoto, @wparad, @Yekongs)
-
Tracking through IDP with individualized account and client_metadata endpoints w3c-fedid/FedCM#700 (9 comments by @hlflanagan, @npm1, @togamid, @wparad)
-
`IdentityProviderBranding` field `name` should provide lang and direction w3c-fedid/FedCM#679 (3 comments by @hlflanagan, @philsmart)
-
login_url not documented in Section 3.2 w3c-fedid/FedCM#697 (3 comments by @cbiesinger, @samuelgoto, @togamid)
-
Algorithm [=attempt to disconnect=] uses optional parameter as required w3c-fedid/FedCM#696 (3 comments by @bvandersloot-mozilla, @cbiesinger, @npm1)
-
`Get Title` doesn't have language or direction metadata w3c-fedid/FedCM#682 (2 comments by @hlflanagan, @npm1)
-
Why is the client_metadata_endpoint required in the config response? w3c-fedid/FedCM#701 (1 comment by @npm1)
-
Allow for language negotiation or localization of privacy policy and TOS? w3c-fedid/FedCM#681 (1 comment by @hlflanagan)
-
Security considerations should be consistently organised by security risk? w3c-fedid/FedCM#685 (1 comment by @philsmart)
-
-
1 pull request opened.
-
Make disconnect options required w3c-fedid/FedCM#699, by @npm1.
-
-
4 pull requests merged.
-
Rewrite security section w3c-fedid/FedCM#692.
-
Mention SameSite cookies in accounts fetch w3c-fedid/FedCM#550.
-
Allow user agent to wait or reject the request before any fetch w3c-fedid/FedCM#676.
-
Make disconnect options required w3c-fedid/FedCM#699.
-
-
4 pull requests received 46 new comments.
-
Add single-get multi IDP support for passive mode w3c-fedid/FedCM#686 (5 comments by @bvandersloot-mozilla, @cbiesinger, @npm1)
-
Specify "Use another account". w3c-fedid/FedCM#678 (4 comments by @bvandersloot-mozilla, @cbiesinger, @TallTed)
w3c-fedid/meetings
-
1 pull request opened.
-
Update 2025-02-25-agenda.md w3c-fedid/meetings#3, by @simoneonofri.
-
-
1 pull request merged.
-
Update 2025-02-25-agenda.md w3c-fedid/meetings#3.
-
w3c-fedid/digital-credentials
-
1 issue opened.
-
Just a little help with credential verification w3c-fedid/digital-credentials#203, by @mmachado53.
-
-
5 issues closed.
-
Managing request format extensibility without sacrificing security w3c-fedid/digital-credentials#102.
-
Just a little help with credential verification w3c-fedid/digital-credentials#203.
-
Explainer: Expand alternatives considered section w3c-fedid/digital-credentials#135.
-
Relying Site/Verifier Lack of Scope or Restrictions w3c-fedid/digital-credentials#187.
-
Visualize transaction data in confirmation dialog w3c-fedid/digital-credentials#195.
-
-
13 issues received 23 new comments.
-
What are the protocol identifier naming rules? w3c-fedid/digital-credentials#191 (4 comments by @bc-pi, @marcoscaceres)
-
Just a little help with credential verification w3c-fedid/digital-credentials#203 (2 comments by @mmachado53, @timcappalli)
-
What is the defined trust boundary between the user, wallet, and browser? w3c-fedid/digital-credentials#166 (2 comments by @kdenhartog, @timcappalli)
-
Managing request format extensibility without sacrificing security w3c-fedid/digital-credentials#102 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#76 (1 comment by @timcappalli)
-
Explainer: Expand alternatives considered section w3c-fedid/digital-credentials#135 (1 comment by @RByers)
-
w3c-fedid/digital-credentials#85 (1 comment by @timcappalli)
-
Relying Site/Verifier Lack of Scope or Restrictions w3c-fedid/digital-credentials#187 (1 comment by @timcappalli)
-
1 pull request opened.
-
Include Digital Credential Issuance in the Spec w3c-fedid/digital-credentials#204, by @mohamedamir.
-
Past meetings
Participants
-
6 participants joined.
-
Ruoxi Ran (W3C) joined.
-
Rene Leveille (1Password) joined.
-
Max Crone (1Password) joined.
-
Nicholas Steele (1Password) joined.
-
Tom Clancy (MITRE Corporation) joined.
-
Henna Kapur (Visa) joined.
-
-
2 organizations joined.
-
1Password joined.
-
Visa joined.
-
GitHub
w3c-fedid/FedCM
-
4 issues opened.
-
Augment autofill with a `conditional` get w3c-fedid/FedCM#694, by @samuelgoto.
-
The project is connected to multiple IdPs w3c-fedid/FedCM#689, by @Yekongs.
-
Missing tasks in parallel steps in Federated Credential Management API w3c-fedid/FedCM#688, by @dontcallmedom-bot.
-
-
3 issues closed.
-
The project is connected to multiple IdPs w3c-fedid/FedCM#689.
-
Profile pictures have to be downloaded before filtering w3c-fedid/FedCM#672.
-
9 issues received 26 new comments.
-
Consider adding an IDP chooser for unconnected IDPs w3c-fedid/FedCM#687 (7 comments by @bvandersloot-mozilla, @npm1, @samuelgoto, @wseltzer)
-
Augment autofill with a `conditional` get w3c-fedid/FedCM#694 (4 comments by @aaronpk, @samuelgoto, @timcappalli)
-
Can RP cache credential.token instead of calling navigator.credentials.get every time the page is refreshed? w3c-fedid/FedCM#691 (3 comments by @npm1, @Yekongs)
-
Clarify the necessity to protect against device exfil attacks w3c-fedid/FedCM#664 (1 comment by @philsmart)
-
w3c-fedid/FedCM#51 (1 comment by @samuelgoto)
-
Security considerations should be consistently organised by security risk? w3c-fedid/FedCM#685 (1 comment by @simoneonofri)
-
-
3 pull requests opened.
-
Remove 'authenticate .... tokens' w3c-fedid/FedCM#693, by @philsmart.
-
Rewrite security section w3c-fedid/FedCM#692, by @npm1.
-
Editorial fixes w3c-fedid/FedCM#690, by @npm1.
-
-
6 pull requests merged.
-
Remove 'authenticate .... tokens' w3c-fedid/FedCM#693.
-
Editorial fixes w3c-fedid/FedCM#690.
-
Remove 'signed assertions about the user' w3c-fedid/FedCM#684.
-
Specify the fields API w3c-fedid/FedCM#668.
-
Replace link to Explainer with Developer Documentation w3c-fedid/FedCM#674.
-
Download profile pictures before filtering accounts w3c-fedid/FedCM#670.
-
-
8 pull requests received 106 new comments.
-
Rewrite security section w3c-fedid/FedCM#692 (52 comments by @npm1, @philsmart, @simoneonofri, @TallTed)
-
Add single-get multi IDP support for passive mode w3c-fedid/FedCM#686 (40 comments by @cbiesinger, @npm1, @TallTed, @wseltzer)
-
Specify the fields API w3c-fedid/FedCM#668 (9 comments by @bvandersloot-mozilla, @cbiesinger, @philsmart, @samuelgoto, @wseltzer)
-
w3c-fedid/digital-credentials
-
4 issues opened.
-
Requests' size should be checked before transient activation w3c-fedid/digital-credentials#202, by @marcoscaceres.
-
multi-wallet requests w3c-fedid/digital-credentials#201, by @Sakurann.
-
Add getClientCapabilities method for feature detection w3c-fedid/digital-credentials#200, by @timcappalli.
-
The digital credential definition should include "verifiable" aspect w3c-fedid/digital-credentials#198, by @marcoscaceres.
-
-
2 issues closed.
-
[spec] Add initial intro text w3c-fedid/digital-credentials#182.
-
[spec] Add blurb about wallets being a second user agent w3c-fedid/digital-credentials#190.
-
-
10 issues received 34 new comments.
-
What are the protocol identifier naming rules? w3c-fedid/digital-credentials#191 (10 comments by @bc-pi, @hlozi, @leecam, @marcoscaceres, @Sakurann, @timcappalli)
-
Visualize transaction data in confirmation dialog w3c-fedid/digital-credentials#195 (7 comments by @leecam, @mobinauten, @timcappalli)
-
Add getClientCapabilities method for feature detection w3c-fedid/digital-credentials#200 (4 comments by @npdoty, @timcappalli)
-
Support for issuance w3c-fedid/digital-credentials#167 (3 comments by @leecam, @npdoty, @samuelgoto)
-
Add a way to check what protocols are supported w3c-fedid/digital-credentials#168 (3 comments by @kdenhartog, @marcoscaceres, @TallTed)
-
The digital credential definition should include "verifiable" aspect w3c-fedid/digital-credentials#198 (1 comment by @timcappalli)
-
Relying Site/Verifier Lack of Scope or Restrictions w3c-fedid/digital-credentials#187 (1 comment by @timcappalli)
-
[spec] Add blurb about wallets being a second user agent w3c-fedid/digital-credentials#190 (1 comment by @timcappalli)
-
-
2 pull requests opened.
-
DigitalCredential's data should be marked at SameObject w3c-fedid/digital-credentials#199, by @marcoscaceres.
-
Editorial: fix typo DigitalCredentialsRequest -> DigitalCredentialRequest w3c-fedid/digital-credentials#196, by @marcoscaceres.
-
-
3 pull requests merged.
-
DigitalCredential's data should be marked at SameObject w3c-fedid/digital-credentials#199.
-
Add initial intro text w3c-fedid/digital-credentials#193.
-
Editorial: fix typo DigitalCredentialsRequest -> DigitalCredentialRequest w3c-fedid/digital-credentials#196.
-
-
4 pull requests received 30 new comments.
-
Add initial intro text w3c-fedid/digital-credentials#193 (27 comments by @marcoscaceres, @RByers, @Ryang03, @samuelgoto, @timcappalli)
-
Require JSON serialization checks coming in w3c-fedid/digital-credentials#179 (1 comment by @marcoscaceres)
-
DigitalCredential's data should be marked at SameObject w3c-fedid/digital-credentials#199 (1 comment by @samuelgoto)
-
w3c-fedid/Administration
-
1 pull request opened.
-
Editorial updates w3c-fedid/Administration#13, by @hlflanagan.
-
-
2 pull requests received 13 new comments.