Federated Identity Working Group - Activity in 2026
No matches.
TR publications
-
2 documents published.
-
Digital Credentials published twice as a Working Draft. History of Digital Credentials
-
Past meetings
Participants
-
1 participant joined.
-
Mallikarjuna Potta (PayPal) joined.
-
-
2 participants left.
-
Christian Bormann (SPRIND GmbH) left.
-
Kristina Yasuda (SPRIND GmbH) left.
-
-
1 organization joined.
-
PayPal joined.
-
-
1 organization left.
-
SPRIND GmbH left.
-
GitHub
w3c-fedid/digital-credentials
-
3 issues opened.
-
Verifier authenticity and ecosystem barrier to entry w3c-fedid/digital-credentials#594, by @wes-smith.
-
Multi-credential flows require a separate wallet handoff for every step w3c-fedid/digital-credentials#593, by @wes-smith.
-
Document the role of architectural layering in the Digital Credentials API w3c-fedid/digital-credentials#589, by @hlflanagan.
-
-
4 issues closed.
-
Protocol Integrity Requirements for Request/Response Tampering w3c-fedid/digital-credentials#494.
-
Adding Signature as Response for Tampering and consider Encryption w3c-fedid/digital-credentials#479.
-
Horizontal Review - Privacy w3c-fedid/digital-credentials#232.
-
Security Considerations: Assumptions (System Layer and Network Layer) w3c-fedid/digital-credentials#273.
-
-
11 issues received 22 new comments.
-
Annex C being optional w3c-fedid/digital-credentials#578 (6 comments by @c2bo, @marcoscaceres, @TallTed)
-
Conditional invocation for Digital Credential presentation requests w3c-fedid/digital-credentials#587 (6 comments by @mallikarjunap, @marcoscaceres, @timcappalli, @wseltzer)
-
Wallet Selection Binding during Issuance w3c-fedid/digital-credentials#382 (2 comments by @c2bo, @leecam)
-
Verifier authenticity and ecosystem barrier to entry w3c-fedid/digital-credentials#594 (1 comment by @donaldzitzer406-lang)
-
Protocol Integrity Requirements for Request/Response Tampering w3c-fedid/digital-credentials#494 (1 comment by @simoneonofri)
-
Adding Signature as Response for Tampering and consider Encryption w3c-fedid/digital-credentials#479 (1 comment by @simoneonofri)
-
Horizontal Review Preparation: DC API w3c-fedid/digital-credentials#227 (1 comment by @marcoscaceres)
-
Define concrete privacy and security requirements for the supported protocols w3c-fedid/digital-credentials#255 (1 comment by @marcoscaceres)
-
Document the role of architectural layering in the Digital Credentials API w3c-fedid/digital-credentials#589 (1 comment by @marcoscaceres)
-
Security Considerations: Assumptions (System Layer and Network Layer) w3c-fedid/digital-credentials#273 (1 comment by @simoneonofri)
-
Rate limiting: implementer considerations w3c-fedid/digital-credentials#495 (1 comment by @marcoscaceres)
-
-
4 pull requests opened.
-
chore: point README and explainer at the new self-review page w3c-fedid/digital-credentials#592, by @marcoscaceres.
-
Editorial: link "object" to the ECMAScript Object type w3c-fedid/digital-credentials#591, by @marcoscaceres.
-
editorial: say when response encryption protects against in-page scripts w3c-fedid/digital-credentials#590, by @marcoscaceres.
-
Proposal: conditional mediation for digital credential presentation requests w3c-fedid/digital-credentials#588, by @mallikarjunap.
-
-
3 pull requests merged.
-
editorial: say when response encryption protects against in-page scripts w3c-fedid/digital-credentials#590.
-
chore: point README and explainer at the new self-review page w3c-fedid/digital-credentials#592, by @marcoscaceres.
-
Editorial: link "object" to the ECMAScript Object type w3c-fedid/digital-credentials#591.
-
-
7 pull requests received 33 new comments.
-
Add verifier hardening guidance for script injection w3c-fedid/digital-credentials#539 (17 comments by @marcoscaceres, @mikewest)
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520 (9 comments by @c2bo, @marcoscaceres, @martijnharing)
-
Editorial: link "object" to the ECMAScript Object type w3c-fedid/digital-credentials#591 (2 comments by @marcoscaceres)
-
Clarify network and protocol tampering threats w3c-fedid/digital-credentials#493 (2 comments by @marcoscaceres)
-
editorial: say when response encryption protects against in-page scripts w3c-fedid/digital-credentials#590 (1 comment by @timcappalli)
-
Proposal: conditional mediation for digital credential presentation requests w3c-fedid/digital-credentials#588 (1 comment by @timcappalli)
-
Apply friction when a request carries no signature to check w3c-fedid/digital-credentials#575 (1 comment by @marcoscaceres)
-
w3c-fedid/FedCM
-
8 issues closed.
-
Support for SAML w3c-fedid/FedCM#479.
-
What is disclosure_text_shown? w3c-fedid/FedCM#475.
-
Autoreauthentication does not work with "silent" mediation value w3c-fedid/FedCM#472.
-
Should FedCM spec have conformance requirements over IDPs w3c-fedid/FedCM#471.
-
Align on user flow for initial and returning FedCM prompts w3c-fedid/FedCM#469.
-
Contextualize account selection w3c-fedid/FedCM#450.
-
The IDP has to support additional infrastructure to support FedCM w3c-fedid/FedCM#441.
-
[Context API] - Authz / relation to ability to specificy scope w3c-fedid/FedCM#407.
-
-
8 issues received 9 new comments.
-
w3c-fedid/FedCM#479 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#475 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#472 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#471 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#469 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#450 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#407 (1 comment by @hlflanagan)
-
2 pull requests opened.
-
Added Privacy Policy, Terms of Service, Account Manager Url fields to IDP Config file w3c-fedid/FedCM#847, by @abhishekmadan30.
-
1 pull request closed.
-
1 pull request received 1 new comment.
-
Strictly Editorial Refactoring to make merging/extending the Registration, Delegation and Accounts Push spec easier w3c-fedid/FedCM#848 (1 comment by @samuelgoto)
-
TR publications
-
2 documents published.
-
Digital Credentials published twice as a Working Draft. History of Digital Credentials
-
Past meetings
Participants
-
2 participants joined.
-
Ling Zhong (Microsoft Corporation) joined.
-
Christian Biesinger (Igalia) joined.
-
-
1 participant left.
-
Torsten Lodderstedt (SPRIND GmbH) left.
-
-
1 organization joined.
-
Igalia joined.
-
GitHub
w3c-fedid/digital-credentials
-
1 issue opened.
-
Conditional invocation for Digital Credential presentation requests w3c-fedid/digital-credentials#587, by @mallikarjunap.
-
-
3 issues closed.
-
Add a diagram showing how things in the model relate to each other w3c-fedid/digital-credentials#66.
-
Update scope around issuance/create to be specific to credential manager selection w3c-fedid/digital-credentials#343.
-
Add testing action to simulate platform error mapping in the "present" algorithm w3c-fedid/digital-credentials#500.
-
-
3 issues received 11 new comments.
-
Annex C being optional w3c-fedid/digital-credentials#578 (8 comments by @bc-pi, @hlflanagan, @marcoscaceres, @TallTed)
-
Add testing action to simulate platform error mapping in the "present" algorithm w3c-fedid/digital-credentials#500 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
Platform-bound wallet attestation for issuance (#382) w3c-fedid/digital-credentials#586, by @mohamedamir.
-
-
3 pull requests merged.
-
Add Credential Manager Chooser def and add clarity around differences with issuance w3c-fedid/digital-credentials#561.
-
Privacy: Add Data Clearing and Credential Availability protections w3c-fedid/digital-credentials#536.
-
Restore the origin-bound declaration on DigitalCredential w3c-fedid/digital-credentials#559.
-
-
9 pull requests received 55 new comments.
-
Add verifier hardening guidance for script injection w3c-fedid/digital-credentials#539 (16 comments by @marcoscaceres, @mikewest, @simoneonofri, @TallTed, @timcappalli)
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520 (11 comments by @marcoscaceres, @mohamedamir, @simoneonofri, @TallTed)
-
Platform-bound wallet attestation for issuance (#382) w3c-fedid/digital-credentials#586 (10 comments by @hlflanagan, @marcoscaceres, @npdoty, @TallTed)
-
Add security considerations on forged credential chooser requests w3c-fedid/digital-credentials#506 (7 comments by @hlflanagan, @marcoscaceres, @mohamedamir, @TallTed)
-
Privacy: Add Data Clearing and Credential Availability protections w3c-fedid/digital-credentials#536 (7 comments by @marcoscaceres, @mohamedamir)
-
Add document origin to request context w3c-fedid/digital-credentials#512 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#585 (1 comment by @w3cbot)
-
Add Credential Manager Chooser def and add clarity around differences with issuance w3c-fedid/digital-credentials#561 (1 comment by @timcappalli)
-
w3c-fedid/digital-credentials#584 (1 comment by @w3cbot)
-
w3c-fedid/FedCM
-
1 issue opened.
-
Unclear as to how the Fields API response is returned in current editors draft w3c-fedid/FedCM#846, by @ThisIsMissEm.
-
-
9 issues received 13 new comments.
-
w3c-fedid/FedCM#479 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#475 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#472 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#471 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#469 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#450 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#441 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#407 (1 comment by @hlflanagan)
-
1 pull request received 5 new comments.
TR publications
-
6 documents published.
-
Digital Credentials published 6 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
7 meetings.
Participants
-
2 participants joined.
-
Naomi Yoshizawa (W3C) joined.
-
Marie Jordan (Visa) joined.
-
-
2 participants left.
-
Christian Biesinger (Igalia) left.
-
Siddhartha Pandey (Microsoft Corporation) left.
-
GitHub
w3c-fedid/digital-credentials
-
6 issues opened.
-
Supporting a "receipt"-style API or callback w3c-fedid/digital-credentials#583, by @timcappalli.
-
空 w3c-fedid/digital-credentials#581, by @turuekarasu0120-star.
-
空 w3c-fedid/digital-credentials#580, by @takagimasao52-cmyk.
-
Annex C being optional w3c-fedid/digital-credentials#578, by @bc-pi.
-
clientData (26H2 edition) w3c-fedid/digital-credentials#574, by @timcappalli.
-
Should we warn the user when a request is not properly protected? w3c-fedid/digital-credentials#571, by @marcoscaceres.
-
-
8 issues closed.
-
EUDI Wallet functional conformance testing w3c-fedid/digital-credentials#471.
-
Define error handling w3c-fedid/digital-credentials#130.
-
空 w3c-fedid/digital-credentials#581.
-
空 w3c-fedid/digital-credentials#580.
-
Unsigned requests can defeat the required response encryption w3c-fedid/digital-credentials#568.
-
User agent request validation and errors w3c-fedid/digital-credentials#472.
-
What protocols should a user agent implement? w3c-fedid/digital-credentials#439.
-
Horizontal Review - Internationalization w3c-fedid/digital-credentials#231.
-
-
1 issue reopened.
-
Define error handling w3c-fedid/digital-credentials#130, by @marcoscaceres.
-
-
9 issues received 22 new comments.
-
Wallet Selection Binding during Issuance w3c-fedid/digital-credentials#382 (5 comments by @hlflanagan, @hlozi, @mohamedamir, @timcappalli, @ve7jtb)
-
EUDI Wallet functional conformance testing w3c-fedid/digital-credentials#471 (3 comments by @hlflanagan, @marcoscaceres)
-
clientData (26H2 edition) w3c-fedid/digital-credentials#574 (3 comments by @hlflanagan, @marcoscaceres)
-
Should we warn the user when a request is not properly protected? w3c-fedid/digital-credentials#571 (3 comments by @bc-pi, @marcoscaceres)
-
Add testing action to simulate platform error mapping in the "present" algorithm w3c-fedid/digital-credentials#500 (1 comment by @marcoscaceres)
-
require in-context in-content explanation and an element for user-initiated presentation w3c-fedid/digital-credentials#208 (1 comment by @hlflanagan)
-
-
3 pull requests opened.
-
Apply friction when a request carries no signature to check w3c-fedid/digital-credentials#575, by @marcoscaceres.
-
Editorial: deduplicate request prologue between get() and create() w3c-fedid/digital-credentials#573, by @mohamedamir.
-
chore: add CI check for committed CRLF line endings w3c-fedid/digital-credentials#572, by @marcoscaceres.
-
-
9 pull requests merged.
-
Security: Expand Threat Model and mitigate malicious payloads w3c-fedid/digital-credentials#533.
-
Add security considerations on signing presentation requests w3c-fedid/digital-credentials#569.
-
Classify validation failures into specific exception types w3c-fedid/digital-credentials#515.
-
Require support for all presentation protocols w3c-fedid/digital-credentials#454.
-
Filter requests to supported protocols before consuming user activation w3c-fedid/digital-credentials#558.
-
Editorial: deduplicate request prologue between get() and create() w3c-fedid/digital-credentials#573.
-
Fail with InvalidStateError when the document is not fully active at call time w3c-fedid/digital-credentials#557.
-
chore: add CI check for committed CRLF line endings w3c-fedid/digital-credentials#572.
-
Explain error behavior in WebDriver extension w3c-fedid/digital-credentials#556.
-
-
2 pull requests closed.
-
Add requestOrigin attribute to DigitalCredential w3c-fedid/digital-credentials#567.
-
All requests must go to client platform for cross-device w3c-fedid/digital-credentials#474.
-
-
25 pull requests received 112 new comments.
-
Add security considerations on signing presentation requests w3c-fedid/digital-credentials#569 (13 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
Require support for all presentation protocols w3c-fedid/digital-credentials#454 (10 comments by @bc-pi, @hlflanagan, @marcoscaceres, @MasterKale, @mohamedamir, @TallTed, @timcappalli)
-
Clarify network and protocol tampering threats w3c-fedid/digital-credentials#493 (9 comments by @marcoscaceres, @mohamedamir, @simoneonofri)
-
Add security considerations on forged credential chooser requests w3c-fedid/digital-credentials#506 (8 comments by @marcoscaceres, @mohamedamir)
-
Restore the origin-bound declaration on DigitalCredential w3c-fedid/digital-credentials#559 (8 comments by @hlflanagan, @marcoscaceres, @mohamedamir)
-
Add Credential Manager Chooser def and add clarity around differences with issuance w3c-fedid/digital-credentials#561 (8 comments by @hlflanagan, @marcoscaceres, @mohamedamir)
-
Add document origin to request context w3c-fedid/digital-credentials#512 (8 comments by @hlflanagan, @marcoscaceres, @TallTed, @timcappalli)
-
Privacy: Add Data Clearing and Credential Availability protections w3c-fedid/digital-credentials#536 (7 comments by @hlflanagan, @marcoscaceres, @mohamedamir)
-
Security: Expand Threat Model and mitigate malicious payloads w3c-fedid/digital-credentials#533 (6 comments by @hlflanagan, @marcoscaceres, @mohamedamir)
-
Classify validation failures into specific exception types w3c-fedid/digital-credentials#515 (5 comments by @hlflanagan, @marcoscaceres, @MasterKale)
-
Privacy Considerations: ecosystem note and per-protocol privacy review w3c-fedid/digital-credentials#543 (4 comments by @marcoscaceres)
-
Editorial: deduplicate request prologue between get() and create() w3c-fedid/digital-credentials#573 (4 comments by @marcoscaceres, @mohamedamir)
-
chore: add CI check for committed CRLF line endings w3c-fedid/digital-credentials#572 (3 comments by @marcoscaceres, @TallTed)
-
Add requestOrigin attribute to DigitalCredential w3c-fedid/digital-credentials#567 (3 comments by @hlflanagan, @marcoscaceres)
-
Add verifier hardening guidance for script injection w3c-fedid/digital-credentials#539 (3 comments by @marcoscaceres, @mohamedamir)
-
Skip requests that fail validation instead of throwing w3c-fedid/digital-credentials#554 (2 comments by @marcoscaceres)
-
Filter requests to supported protocols before consuming user activation w3c-fedid/digital-credentials#558 (2 comments by @marcoscaceres, @mohamedamir)
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520 (2 comments by @marcoscaceres, @wseltzer)
-
w3c-fedid/digital-credentials#582 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#579 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#577 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#576 (1 comment by @w3cbot)
-
Apply friction when a request carries no signature to check w3c-fedid/digital-credentials#575 (1 comment by @MasterKale)
-
All requests must go to client platform for cross-device w3c-fedid/digital-credentials#474 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#570 (1 comment by @w3cbot)
-
w3c-fedid/FedCM
-
7 issues closed.
-
Add note about PP / TOS w3c-fedid/FedCM#312.
-
Clarify the IDP API response when the user is not signed in. w3c-fedid/FedCM#218.
-
Support for RP controls to support meaningful integration into their user flows w3c-fedid/FedCM#348.
-
[Technical] Manifest fetching should happen sequentially w3c-fedid/FedCM#293.
-
Support for cascaded/staged federation scenarios w3c-fedid/FedCM#264.
-
Additional Use-Cases: Active Session Discovery, Auto Sign-On w3c-fedid/FedCM#14.
-
Conceptual Scope w.r.t. OpenID Connect/OAuth 2.0 w3c-fedid/FedCM#5.
-
-
10 issues received 12 new comments.
-
Specify the border between FedCM and protocols building on it w3c-fedid/FedCM#764 (3 comments by @okayame702-png)
-
w3c-fedid/FedCM#380 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#312 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#218 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#348 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#293 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#264 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#14 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#5 (1 comment by @hlflanagan)
-
-
1 pull request received 14 new comments.
-
Add initial Identity Handler SW Registration Tie In. w3c-fedid/FedCM#842 (14 comments by @Brandr0id, @npm1)
-
w3c-fedid/meetings
-
1 pull request opened.
-
Update notes on requestOrigin attribute discussion w3c-fedid/meetings#7, by @TallTed.
-
TR publications
-
3 documents published.
-
Digital Credentials published 3 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
6 meetings.
Participants
-
2 participants joined.
-
Brandon Maslen (Microsoft Corporation) joined.
-
Jarek Sygitowicz (W3C Invited Experts) joined.
-
-
2 participants left.
-
Tom Clancy (MITRE Corporation) left.
-
Emily Lauber (Microsoft Corporation) left.
-
-
1 organization left.
-
MITRE Corporation left.
-
GitHub
w3c-fedid/digital-credentials
-
6 issues opened.
-
Unsigned requests can defeat the required response encryption w3c-fedid/digital-credentials#568, by @marcoscaceres.
-
API does not expose the origin context used for response encryption w3c-fedid/digital-credentials#566, by @marcoscaceres.
-
Update CTAP 2.3 reference to PXP w3c-fedid/digital-credentials#565, by @timcappalli.
-
Prohibit delegating coordinator responsibilities to a credential manager without explicit permission w3c-fedid/digital-credentials#563, by @jschanck.
-
Move the opaque-origin rejection to Credential Management, keyed on origin bound w3c-fedid/digital-credentials#560, by @marcoscaceres.
-
clearing local storage should be communicated to wallets so as not to reintroduce cookie-like keys/signatures w3c-fedid/digital-credentials#551, by @npdoty.
-
-
4 issues closed.
-
Presenting with CTAP w3c-fedid/digital-credentials#456.
-
Add details about the Cross-device experience for the Digital Credentials API w3c-fedid/digital-credentials#369.
-
Add a signal of whether presentation occurred locally or cross-device w3c-fedid/digital-credentials#527.
-
Add DigitalCredentialIssuanceResponse partial w3c-fedid/digital-credentials#356.
-
-
8 issues received 18 new comments.
-
Unsigned requests can defeat the required response encryption w3c-fedid/digital-credentials#568 (5 comments by @c2bo, @marcoscaceres)
-
Add a signal of whether presentation occurred locally or cross-device w3c-fedid/digital-credentials#527 (5 comments by @hlflanagan, @marcoscaceres, @MasterKale, @timcappalli)
-
Add details about the Cross-device experience for the Digital Credentials API w3c-fedid/digital-credentials#369 (2 comments by @hlflanagan, @marcoscaceres)
-
Define DC API behavior in Private Browsing Mode w3c-fedid/digital-credentials#416 (2 comments by @bc-pi, @timcappalli)
-
clearing local storage should be communicated to wallets so as not to reintroduce cookie-like keys/signatures w3c-fedid/digital-credentials#551 (1 comment by @timcappalli)
-
require in-context in-content explanation and an element for user-initiated presentation w3c-fedid/digital-credentials#208 (1 comment by @npdoty)
-
Should we normatively define elements of a permission prompt? w3c-fedid/digital-credentials#252 (1 comment by @marcoscaceres)
-
Add DigitalCredentialIssuanceResponse partial w3c-fedid/digital-credentials#356 (1 comment by @mohamedamir)
-
-
11 pull requests opened.
-
Add security considerations on signing presentation requests w3c-fedid/digital-credentials#569, by @marcoscaceres.
-
Add requestOrigin attribute to DigitalCredential w3c-fedid/digital-credentials#567, by @marcoscaceres.
-
Privacy Considerations: Issuer identity in selective disclosure cases w3c-fedid/digital-credentials#564, by @simoneonofri.
-
Private Browsing mode w3c-fedid/digital-credentials#562, by @timcappalli.
-
Add Credential Manager Chooser def and add clarity around differences with issuance w3c-fedid/digital-credentials#561, by @timcappalli.
-
Restore the origin-bound declaration on DigitalCredential w3c-fedid/digital-credentials#559, by @marcoscaceres.
-
Filter requests to supported protocols before consuming user activation w3c-fedid/digital-credentials#558, by @marcoscaceres.
-
Fail with InvalidStateError when the document is not fully active at call time w3c-fedid/digital-credentials#557, by @marcoscaceres.
-
Explain error behavior in WebDriver extension w3c-fedid/digital-credentials#556, by @mohamedamir.
-
Skip requests that fail validation instead of throwing w3c-fedid/digital-credentials#554, by @marcoscaceres.
-
Issuance request forwarding: Documenting the threat w3c-fedid/digital-credentials#550, by @simoneonofri.
-
-
7 pull requests merged.
-
editorial: fix closure capture, parameter type, and grammar w3c-fedid/digital-credentials#505.
-
API: Recommend CTAP/PXP for cross-device credential exchanges w3c-fedid/digital-credentials#540.
-
Security: Add cross-device security and proximity considerations w3c-fedid/digital-credentials#538.
-
Expand Accessibility Considerations section w3c-fedid/digital-credentials#542.
-
Add Internationalization Considerations section w3c-fedid/digital-credentials#541.
-
Prevent opaque origins from interacting with the Digital Credentials API w3c-fedid/digital-credentials#535.
-
fix: abort a waiting request when its document is torn down w3c-fedid/digital-credentials#549.
-
-
2 pull requests closed.
-
Privacy: Define expectations for Private Browsing (Incognito) Mode w3c-fedid/digital-credentials#534.
-
Add DigitalCredential.issue() for credential issuance w3c-fedid/digital-credentials#546.
-
-
21 pull requests received 75 new comments.
-
Classify validation failures into specific exception types w3c-fedid/digital-credentials#515 (11 comments by @hlflanagan, @marcoscaceres, @MasterKale, @TallTed, @timcappalli)
-
Add document origin to request context w3c-fedid/digital-credentials#512 (9 comments by @hlflanagan, @marcoscaceres, @TallTed)
-
Prevent opaque origins from interacting with the Digital Credentials API w3c-fedid/digital-credentials#535 (9 comments by @hlflanagan, @marcoscaceres, @mohamedamir)
-
Security: Add cross-device security and proximity considerations w3c-fedid/digital-credentials#538 (8 comments by @c2bo, @hlflanagan, @marcoscaceres, @mohamedamir, @timcappalli)
-
Add verifier hardening guidance for script injection w3c-fedid/digital-credentials#539 (7 comments by @c2bo, @hlflanagan, @marcoscaceres, @TallTed, @timcappalli)
-
Privacy Considerations: Issuer identity in selective disclosure cases w3c-fedid/digital-credentials#564 (4 comments by @TallTed)
-
Privacy: Define expectations for Private Browsing (Incognito) Mode w3c-fedid/digital-credentials#534 (4 comments by @hlflanagan, @mohamedamir, @npdoty)
-
Require support for all presentation protocols w3c-fedid/digital-credentials#454 (3 comments by @hlflanagan, @TallTed)
-
Issuance request forwarding: Documenting the threat w3c-fedid/digital-credentials#550 (3 comments by @c2bo, @marcoscaceres, @TallTed)
-
API: Recommend CTAP/PXP for cross-device credential exchanges w3c-fedid/digital-credentials#540 (3 comments by @marcoscaceres, @mohamedamir)
-
Explain error behavior in WebDriver extension w3c-fedid/digital-credentials#556 (2 comments by @marcoscaceres)
-
Expand Accessibility Considerations section w3c-fedid/digital-credentials#542 (2 comments by @hlflanagan)
-
Add Internationalization Considerations section w3c-fedid/digital-credentials#541 (2 comments by @hlflanagan)
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520 (1 comment by @TallTed)
-
editorial: fix closure capture, parameter type, and grammar w3c-fedid/digital-credentials#505 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#555 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#553 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#552 (1 comment by @w3cbot)
-
fix: abort a waiting request when its document is torn down w3c-fedid/digital-credentials#549 (1 comment by @marcoscaceres)
-
Add DigitalCredential.issue() for credential issuance w3c-fedid/digital-credentials#546 (1 comment by @marcoscaceres)
-
w3c-fedid/FedCM
-
6 issues opened.
-
In the `continue_on` API, allow IdPs to control min/max width/height of the pop-up window w3c-fedid/FedCM#845, by @samuelgoto.
-
Add support for `birthday` to the list of recognized fields w3c-fedid/FedCM#844, by @samuelgoto.
-
Obtaining access tokens via FedCM w3c-fedid/FedCM#843, by @gffletch.
-
CSP integration seems incorrect w3c-fedid/FedCM#838, by @annevk.
-
ชอบมั่วคอนเทนต์ w3c-fedid/FedCM#836, by @noirnear09-web.
-
`credential.get()` for both Passkey and FedCM in one call - what's the plan? w3c-fedid/FedCM#835, by @cgrushko.
-
-
29 issues closed.
-
Value of Sec-FedCM-CSRF header in discovery call? w3c-fedid/FedCM#267.
-
Share performance measurement with IDP w3c-fedid/FedCM#352.
-
IdP requires knowlege of RP to allow a session w3c-fedid/FedCM#377.
-
ASCII art? w3c-fedid/FedCM#332.
-
manifest relative URL issue w3c-fedid/FedCM#266.
-
Branding JSON - dark mode vs light w3c-fedid/FedCM#246.
-
Resource Access 1.1.5 interaction model is vague w3c-fedid/FedCM#244.
-
Privacy unfriendly account chooser w3c-fedid/FedCM#242.
-
Erroneous link to JSON object in automation section of spec w3c-fedid/FedCM#487.
-
Cookie headers in examples are incorrect w3c-fedid/FedCM#825.
-
Which cookies are sent with FedCM requests? w3c-fedid/FedCM#824.
-
Allow user agents to use "Connected Accounts Set" with flexibility w3c-fedid/FedCM#517.
-
Support classic websites (non-javascript applications) w3c-fedid/FedCM#241.
-
Multi-tenant considerations with endpoint metadata w3c-fedid/FedCM#153.
-
Should FederatedCredential be FederatedCredential2? w3c-fedid/FedCM#237.
-
Leverage users' prior relationships with their IdPs w3c-fedid/FedCM#58.
-
Directed identifiers problematic for efforts around portable identities w3c-fedid/FedCM#56.
-
Missing use cases w3c-fedid/FedCM#253.
-
Nested Frame Support w3c-fedid/FedCM#44.
-
Extend WebID for parity or improved device compliance and SSO support w3c-fedid/FedCM#50.
-
Extend support for identities known by the User Agent and Host OS w3c-fedid/FedCM#51.
-
Privacy of Directed Identifiers and Competitive consequences of centralized IDPs w3c-fedid/FedCM#42.
-
First party consumer SSO w3c-fedid/FedCM#26.
-
Authentication-only proposal - AcctAuthn w3c-fedid/FedCM#33.
-
ชอบมั่วคอนเทนต์ w3c-fedid/FedCM#836.
-
-
39 issues received 69 new comments.
-
`credential.get()` for both Passkey and FedCM in one call - what's the plan? w3c-fedid/FedCM#835 (4 comments by @cgrushko, @npm1, @samuelgoto)
-
w3c-fedid/FedCM#352 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#377 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#332 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#266 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#246 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#244 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#242 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#241 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#230 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#153 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#237 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#64 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#58 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#56 (2 comments by @hlflanagan)
-
w3c-fedid/FedCM#348 (1 comment by @hlflanagan)
-
Is the current the definition of "core" backwards incompatible? w3c-fedid/FedCM#714 (1 comment by @hlflanagan)
-
Does "core" need to introduce feature detection for features in "extensions"? w3c-fedid/FedCM#713 (1 comment by @hlflanagan)
-
FedCM "core": break Web Platform tests between "core" and "extensions" w3c-fedid/FedCM#704 (1 comment by @hlflanagan)
-
FedCM "core": move "extensions" out of the current spec into an independent spec w3c-fedid/FedCM#703 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#253 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#293 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#264 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#42 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#14 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM#5 (1 comment by @hlflanagan)
-
-
5 pull requests opened.
-
Add initial Identity Handler SW Registration Tie In. w3c-fedid/FedCM#842, by @Brandr0id.
-
Fix ECMAScript Object link references in WebDriver steps w3c-fedid/FedCM#841, by @npm1.
-
Clarify UI formulation flexibility and cooldowns in spec algorithms w3c-fedid/FedCM#840, by @npm1.
-
Fix Cookie header examples and SameSite typo w3c-fedid/FedCM#839, by @npm1.
-
Disambiguate 'success' definition reference in Bikeshed link defaults w3c-fedid/FedCM#837, by @npm1.
-
-
5 pull requests merged.
-
Fix ECMAScript Object link references in WebDriver steps w3c-fedid/FedCM#841.
-
Clarify UI formulation flexibility and cooldowns in spec algorithms w3c-fedid/FedCM#840.
-
Fix Cookie header examples and SameSite typo w3c-fedid/FedCM#839.
-
Add third party cookie relaxations for FedCM w3c-fedid/FedCM#523.
-
Disambiguate 'success' definition reference in Bikeshed link defaults w3c-fedid/FedCM#837.
-
-
3 pull requests received 43 new comments.
-
Add initial Identity Handler SW Registration Tie In. w3c-fedid/FedCM#842 (34 comments by @Brandr0id, @monica-ch, @npm1, @TallTed, @yoshisatoyanagisawa)
-
Clarify UI formulation flexibility and cooldowns in spec algorithms w3c-fedid/FedCM#840 (2 comments by @TallTed)
-
TR publications
-
4 documents published.
-
Digital Credentials published 4 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
7 meetings.
Participants
-
2 participants joined.
-
Sindhoor Grandhi (Microsoft Corporation) joined.
-
Tejas Dhagawkar (Microsoft Corporation) joined.
-
-
1 participant left.
-
Henna Kapur (Visa) left.
-
GitHub
w3c-fedid/digital-credentials
-
3 issues opened.
-
MasterCard w3c-fedid/digital-credentials#548, by @livelifestressless2-pixel.
-
Should presenting both origins for cross-origin requests be a MUST? w3c-fedid/digital-credentials#545, by @marcoscaceres.
-
Add a signal of whether presentation occurred locally or cross-device w3c-fedid/digital-credentials#527, by @MasterKale.
-
-
17 issues closed.
-
MasterCard w3c-fedid/digital-credentials#548.
-
Should presenting both origins for cross-origin requests be a MUST? w3c-fedid/digital-credentials#545.
-
Privacy Considerations for Cross-Device Flows w3c-fedid/digital-credentials#400.
-
Security/Privacy Considerations: Trust boundaries between the Wallet and the Browser? w3c-fedid/digital-credentials#269.
-
This API should address the Jevons Paradox around increased consumption of verifiable credentials and the rise of their abuses w3c-fedid/digital-credentials#35.
-
Choice of issuers and consequent exclusion risk w3c-fedid/digital-credentials#298.
-
define consent and permission; explain split roles regarding consent w3c-fedid/digital-credentials#290.
-
note designed-for-purpose alternatives and the risk of crowding out those options w3c-fedid/digital-credentials#289.
-
friction and frequency minimization w3c-fedid/digital-credentials#268.
-
multi-wallet requests w3c-fedid/digital-credentials#201.
-
Should we have a common and interoperable definition of request types and their privacy properties? w3c-fedid/digital-credentials#117.
-
Tradeoffs of being more or less conservative in DC API velocity w3c-fedid/digital-credentials#106.
-
Privacy: ensuring RPs blinded to credential existence w3c-fedid/digital-credentials#105.
-
Most users will experience a no-matching-credential dead-end w3c-fedid/digital-credentials#104.
-
registry of credential types w3c-fedid/digital-credentials#85.
-
what restrictions can the issuer put on wallets that it provisions into? w3c-fedid/digital-credentials#84.
-
API requests should provide the site with what they need to explain why and how requested credential information will be used w3c-fedid/digital-credentials#44.
-
-
32 issues received 49 new comments.
-
Spec doesn’t enforce encrypted response requirement w3c-fedid/digital-credentials#519 (6 comments by @alexlingerie, @hlflanagan, @hlozi, @simoneonofri)
-
Clarify the relationship and trust model of multiple user agents w3c-fedid/digital-credentials#263 (4 comments by @hlflanagan, @marcoscaceres, @simoneonofri)
-
Add DigitalCredentialIssuanceResponse partial w3c-fedid/digital-credentials#356 (3 comments by @marcoscaceres, @MasterKale)
-
Wallet Selection Binding during Issuance w3c-fedid/digital-credentials#382 (2 comments by @hlflanagan, @tejasdhagawkar01)
-
registration of and commitment to a particular use case and purpose w3c-fedid/digital-credentials#266 (2 comments by @hlflanagan, @zoracon)
-
EUDI Wallet functional conformance testing w3c-fedid/digital-credentials#471 (2 comments by @marcoscaceres, @simoneonofri)
-
Horizontal Review - Internationalization w3c-fedid/digital-credentials#231 (2 comments by @marcoscaceres)
-
Add a signal of whether presentation occurred locally or cross-device w3c-fedid/digital-credentials#527 (2 comments by @kkoiwai, @marcoscaceres)
-
Should presenting both origins for cross-origin requests be a MUST? w3c-fedid/digital-credentials#545 (1 comment by @marcoscaceres)
-
Privacy Considerations for Cross-Device Flows w3c-fedid/digital-credentials#400 (1 comment by @mohamedamir)
-
Security/Privacy Considerations: Trust boundaries between the Wallet and the Browser? w3c-fedid/digital-credentials#269 (1 comment by @simoneonofri)
-
Top frame origin should be passed to client platforms and credential managers for cross-origin requests w3c-fedid/digital-credentials#333 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#35 (1 comment by @marcoscaceres)
-
voluntary usage and protections against coercion w3c-fedid/digital-credentials#265 (1 comment by @hlflanagan)
-
Choice of issuers and consequent exclusion risk w3c-fedid/digital-credentials#298 (1 comment by @hlflanagan)
-
define consent and permission; explain split roles regarding consent w3c-fedid/digital-credentials#290 (1 comment by @hlflanagan)
-
note designed-for-purpose alternatives and the risk of crowding out those options w3c-fedid/digital-credentials#289 (1 comment by @hlflanagan)
-
Should we have a common and interoperable definition of request types and their privacy properties? w3c-fedid/digital-credentials#117 (1 comment by @hlflanagan)
-
Tradeoffs of being more or less conservative in DC API velocity w3c-fedid/digital-credentials#106 (1 comment by @hlflanagan)
-
Privacy: ensuring RPs blinded to credential existence w3c-fedid/digital-credentials#105 (1 comment by @hlflanagan)
-
Most users will experience a no-matching-credential dead-end w3c-fedid/digital-credentials#104 (1 comment by @hlflanagan)
-
w3c-fedid/digital-credentials#85 (1 comment by @hlflanagan)
-
w3c-fedid/digital-credentials#84 (1 comment by @hlflanagan)
-
w3c-fedid/digital-credentials#44 (1 comment by @hlflanagan)
-
Paths towards resolution on the registry [TPAC] w3c-fedid/digital-credentials#396 (1 comment by @carrerabenjamin792-dev)
-
-
21 pull requests opened.
-
fix: abort a waiting request when its document is torn down w3c-fedid/digital-credentials#549, by @marcoscaceres.
-
editorial: drop redundant pre-abort check in [[DiscoverFromExternalSource]] w3c-fedid/digital-credentials#547, by @marcoscaceres.
-
Add DigitalCredential.issue() for credential issuance w3c-fedid/digital-credentials#546, by @marcoscaceres.
-
Privacy Considerations: proposed privacy and security requirements for presentation protocols w3c-fedid/digital-credentials#544, by @marcoscaceres.
-
Privacy Considerations: ecosystem note and per-protocol privacy review w3c-fedid/digital-credentials#543, by @marcoscaceres.
-
Expand Accessibility Considerations section w3c-fedid/digital-credentials#542, by @marcoscaceres.
-
Add Internationalization Considerations section w3c-fedid/digital-credentials#541, by @marcoscaceres.
-
API: Recommend CTAP/PXP for cross-device credential exchanges w3c-fedid/digital-credentials#540, by @mohamedamir.
-
Add verifier hardening guidance for script injection w3c-fedid/digital-credentials#539, by @marcoscaceres.
-
Security: Add cross-device security and proximity considerations w3c-fedid/digital-credentials#538, by @mohamedamir.
-
Privacy: Add Data Clearing and Credential Availability protections w3c-fedid/digital-credentials#536, by @mohamedamir.
-
Prevent opaque origins from interacting with the Digital Credentials API w3c-fedid/digital-credentials#535, by @mohamedamir.
-
Privacy: Define expectations for Private Browsing (Incognito) Mode w3c-fedid/digital-credentials#534, by @mohamedamir.
-
Security: Expand Threat Model and mitigate malicious payloads w3c-fedid/digital-credentials#533, by @mohamedamir.
-
Address missing sections for Security and Privacy Self-Review Questionnaire w3c-fedid/digital-credentials#532, by @mohamedamir.
-
Update API to return an array of DigitalCredential instances w3c-fedid/digital-credentials#531, by @mohamedamir.
-
Update API to return an array of DigitalCredential instances w3c-fedid/digital-credentials#530, by @mohamedamir.
-
Privacy Considerations: state the user agent's baseline linkability assumption w3c-fedid/digital-credentials#528, by @marcoscaceres.
-
Apply small editorial wording fixes w3c-fedid/digital-credentials#526, by @marcoscaceres.
-
editorial: privacy and security reference modernization and prose cleanup w3c-fedid/digital-credentials#525, by @marcoscaceres.
-
chore: Modernize ReSpec references w3c-fedid/digital-credentials#524, by @marcoscaceres.
-
-
5 pull requests merged.
-
editorial: drop redundant pre-abort check in [[DiscoverFromExternalSource]] w3c-fedid/digital-credentials#547.
-
editorial: extract "Convert request protocol" as standalone algorithm w3c-fedid/digital-credentials#522.
-
editorial: privacy and security reference modernization and prose cleanup w3c-fedid/digital-credentials#525.
-
Apply small editorial wording fixes w3c-fedid/digital-credentials#526.
-
chore: Modernize ReSpec references w3c-fedid/digital-credentials#524.
-
-
2 pull requests closed.
-
Address missing sections for Security and Privacy Self-Review Questionnaire w3c-fedid/digital-credentials#532.
-
Update API to return an array of DigitalCredential instances w3c-fedid/digital-credentials#530.
-
-
20 pull requests received 64 new comments.
-
Privacy Considerations: ecosystem note and per-protocol privacy review w3c-fedid/digital-credentials#543 (8 comments by @marcoscaceres, @TallTed)
-
Add verifier hardening guidance for script injection w3c-fedid/digital-credentials#539 (7 comments by @marcoscaceres, @simoneonofri)
-
API: Recommend CTAP/PXP for cross-device credential exchanges w3c-fedid/digital-credentials#540 (6 comments by @marcoscaceres, @TallTed, @timcappalli)
-
Expand Accessibility Considerations section w3c-fedid/digital-credentials#542 (6 comments by @TallTed)
-
Add DigitalCredential.issue() for credential issuance w3c-fedid/digital-credentials#546 (5 comments by @c2bo, @hlflanagan, @marcoscaceres, @timcappalli)
-
Security: Expand Threat Model and mitigate malicious payloads w3c-fedid/digital-credentials#533 (5 comments by @marcoscaceres, @TallTed)
-
Apply small editorial wording fixes w3c-fedid/digital-credentials#526 (5 comments by @marcoscaceres, @mohamedamir)
-
Privacy: Define expectations for Private Browsing (Incognito) Mode w3c-fedid/digital-credentials#534 (4 comments by @marcoscaceres)
-
Security: Add cross-device security and proximity considerations w3c-fedid/digital-credentials#538 (3 comments by @TallTed)
-
Privacy Considerations: state the user agent's baseline linkability assumption w3c-fedid/digital-credentials#528 (3 comments by @TallTed, @timcappalli)
-
Replace mediation "MUST NOT throw" prose with [[implicitMediation]] slot w3c-fedid/digital-credentials#511 (2 comments by @marcoscaceres)
-
Address missing sections for Security and Privacy Self-Review Questionnaire w3c-fedid/digital-credentials#532 (2 comments by @marcoscaceres, @mohamedamir)
-
fix: abort a waiting request when its document is torn down w3c-fedid/digital-credentials#549 (1 comment by @marcoscaceres)
-
Prevent opaque origins from interacting with the Digital Credentials API w3c-fedid/digital-credentials#535 (1 comment by @RByers)
-
Require support for all presentation protocols w3c-fedid/digital-credentials#454 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#537 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#529 (1 comment by @w3cbot)
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520 (1 comment by @hlflanagan)
-
Relax transient activation requirement for DC API requests w3c-fedid/digital-credentials#486 (1 comment by @hlflanagan)
-
w3c-fedid/FedCM
-
4 issues received 29 new comments.
-
Remaining items to resolve in IDP Service Worker design w3c-fedid/FedCM#833 (22 comments by @ajaysrrinivas, @domfarolino, @hlflanagan, @mikewest, @npm1, @pottis, @wanderview, @yoshisatoyanagisawa)
-
FedCM facilitates vendor lock-in w3c-fedid/FedCM#827 (5 comments by @hlflanagan, @npm1, @will-bartlett, @wseltzer)
-
w3c-fedid/FedCM#333 (1 comment by @wseltzer)
-
-
1 pull request opened.
-
Add FedCM service worker registration and lifecycle model w3c-fedid/FedCM#834, by @ajaysrrinivas.
-
-
1 pull request merged.
-
Add FedCM service worker registration and lifecycle model w3c-fedid/FedCM#834.
-
-
2 pull requests received 3 new comments.
-
Add FedCM service worker registration and lifecycle model w3c-fedid/FedCM#834 (1 comment by @samuelgoto)
w3c-fedid/meetings
-
1 pull request opened.
-
Fix a transcription error w3c-fedid/meetings#6, by @cbiesinger.
-
TR publications
-
5 documents published.
-
Digital Credentials published 5 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
6 meetings.
Participants
-
3 participants joined.
-
Prashant Singh (Microsoft Corporation) joined.
-
Sami Tikkala (Visa) joined.
-
Emanuel Silva (HM Government) joined.
-
GitHub
w3c-fedid/digital-credentials
-
4 issues opened.
-
https://developers.google.com/issue-tracker/concepts/issues?hl=es-419#issue_access_limits w3c-fedid/digital-credentials#523, by @perezcimamarcoantonio-dotcom.
-
Spec doesn’t enforce encrypted response requirement w3c-fedid/digital-credentials#519, by @marcoscaceres.
-
Replace "MUST NOT throw" mediation prose with [[implicitMediation]] slot w3c-fedid/digital-credentials#510, by @marcoscaceres.
-
Remove "origin bound" declaration from DigitalCredential w3c-fedid/digital-credentials#508, by @marcoscaceres.
-
-
24 issues closed.
-
https://developers.google.com/issue-tracker/concepts/issues?hl=es-419#issue_access_limits w3c-fedid/digital-credentials#523.
-
Handling various origin types w3c-fedid/digital-credentials#160.
-
Security Considerations section w3c-fedid/digital-credentials#274.
-
Terms: Use "credential manager" in technical references w3c-fedid/digital-credentials#414.
-
Terms: link "credential manager" to CredMan w3c-fedid/digital-credentials#412.
-
Rename Model to Terminology w3c-fedid/digital-credentials#410.
-
Terminology Updates and Additions w3c-fedid/digital-credentials#409.
-
enumerated values for purpose, sharing and retention in API method w3c-fedid/digital-credentials#209.
-
Add getClientCapabilities method for feature detection w3c-fedid/digital-credentials#200.
-
Create an issue template for registration w3c-fedid/digital-credentials#223.
-
The digital credential definition should include "verifiable" aspect w3c-fedid/digital-credentials#198.
-
Terms: Add "wallet" and "digital wallet" with alias to credential manager w3c-fedid/digital-credentials#413.
-
Terms: add issuer service and verifier service w3c-fedid/digital-credentials#411.
-
Threat Modeling for Decentralized Identities w3c-fedid/digital-credentials#115.
-
Access to an Open Global Web Reduced w3c-fedid/digital-credentials#123.
-
Remove "origin bound" declaration from DigitalCredential w3c-fedid/digital-credentials#508.
-
Should response encryption be required w3c-fedid/digital-credentials#109.
-
Add means to test Digital Credentials API w3c-fedid/digital-credentials#357.
-
Privacy Considerations: Addressing "unnecessary" usage of the API w3c-fedid/digital-credentials#243.
-
Privacy Considerations: Preventing information leakage and fingerprinting w3c-fedid/digital-credentials#245.
-
Privacy Considerations: "Spectrum of Privacy" w3c-fedid/digital-credentials#242.
-
What is the defined trust boundary between the user, wallet, and browser? w3c-fedid/digital-credentials#166.
-
Consider applying the robustness principle with regard to user agent request validation w3c-fedid/digital-credentials#100.
-
Link up defined terms w3c-fedid/digital-credentials#394.
-
-
34 issues received 68 new comments.
-
Spec doesn’t enforce encrypted response requirement w3c-fedid/digital-credentials#519 (13 comments by @bc-pi, @c2bo, @hlflanagan, @leecam, @marcoscaceres, @mohamedamir, @timcappalli)
-
w3c-fedid/digital-credentials#35 (13 comments by @c2bo, @DemiMarie, @hlflanagan, @kdenhartog, @marcoscaceres, @timcappalli)
-
What is the defined trust boundary between the user, wallet, and browser? w3c-fedid/digital-credentials#166 (3 comments by @hlflanagan, @kdenhartog, @timcappalli)
-
Should we normatively define elements of a permission prompt? w3c-fedid/digital-credentials#252 (2 comments by @hlflanagan, @johannhof)
-
Handling various origin types w3c-fedid/digital-credentials#160 (2 comments by @marcoscaceres, @timcappalli)
-
Access to an Open Global Web Reduced w3c-fedid/digital-credentials#123 (2 comments by @bvandersloot-mozilla, @hlflanagan)
-
Terms: Use "credential manager" in technical references w3c-fedid/digital-credentials#414 (1 comment by @marcoscaceres)
-
Terms: link "credential manager" to CredMan w3c-fedid/digital-credentials#412 (1 comment by @marcoscaceres)
-
Define concrete privacy and security requirements for the supported protocols w3c-fedid/digital-credentials#255 (1 comment by @hlflanagan)
-
Privacy Considerations: Types of Wallets and trust in different Wallets w3c-fedid/digital-credentials#246 (1 comment by @hlflanagan)
-
Handling Multiple Credentials from Different Wallets in DC API Presentation Responses w3c-fedid/digital-credentials#222 (1 comment by @hlflanagan)
-
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)
-
Add getClientCapabilities method for feature detection w3c-fedid/digital-credentials#200 (1 comment by @hlflanagan)
-
Terms: Add "wallet" and "digital wallet" with alias to credential manager w3c-fedid/digital-credentials#413 (1 comment by @timcappalli)
-
Terms: add issuer service and verifier service w3c-fedid/digital-credentials#411 (1 comment by @timcappalli)
-
Threat Modeling for Decentralized Identities w3c-fedid/digital-credentials#115 (1 comment by @simoneonofri)
-
Privacy Considerations: Addressing "unnecessary" usage of the API w3c-fedid/digital-credentials#243 (1 comment by @johannhof)
-
Privacy Considerations: Preventing information leakage and fingerprinting w3c-fedid/digital-credentials#245 (1 comment by @johannhof)
-
Privacy Considerations: "Spectrum of Privacy" w3c-fedid/digital-credentials#242 (1 comment by @johannhof)
-
Include the requesting document's origin in the request context w3c-fedid/digital-credentials#504 (1 comment by @marcoscaceres)
-
Issuer identity in selective disclosure cases w3c-fedid/digital-credentials#139 (1 comment by @hlflanagan)
-
Consider requiring a strong signal of user intent. w3c-fedid/digital-credentials#134 (1 comment by @hlflanagan)
-
Should requests be assumed to be linkable by the browser? w3c-fedid/digital-credentials#122 (1 comment by @hlflanagan)
-
Most users will experience a no-matching-credential dead-end w3c-fedid/digital-credentials#104 (1 comment by @hlflanagan)
-
Should we have a common and interoperable definition of request types and their privacy properties? w3c-fedid/digital-credentials#117 (1 comment by @timcappalli)
-
Consider applying the robustness principle with regard to user agent request validation w3c-fedid/digital-credentials#100 (1 comment by @timcappalli)
-
-
9 pull requests opened.
-
editorial: extract "Convert request protocol" as standalone algorithm w3c-fedid/digital-credentials#522, by @marcoscaceres.
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520, by @marcoscaceres.
-
editorial: Tweak cross-origin example w3c-fedid/digital-credentials#517, by @timcappalli.
-
editorial: Terminology Updates w3c-fedid/digital-credentials#516, by @timcappalli.
-
Classify validation failures into specific exception types w3c-fedid/digital-credentials#515, by @marcoscaceres.
-
editorial: Fix WebDriver session links in Automated Testing section w3c-fedid/digital-credentials#514, by @mohamedamir.
-
Add document origin to request context w3c-fedid/digital-credentials#512, by @marcoscaceres.
-
Replace mediation "MUST NOT throw" prose with [[implicitMediation]] slot w3c-fedid/digital-credentials#511, by @marcoscaceres.
-
Remove "origin bound" declaration from DigitalCredential w3c-fedid/digital-credentials#509, by @marcoscaceres.
-
-
7 pull requests merged.
-
editorial: Tweak cross-origin example w3c-fedid/digital-credentials#517.
-
editorial: Terminology Updates w3c-fedid/digital-credentials#516.
-
Remove "origin bound" declaration from DigitalCredential w3c-fedid/digital-credentials#509.
-
editorial: Fix WebDriver session links in Automated Testing section w3c-fedid/digital-credentials#514.
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381.
-
Add API Flooding security considerations w3c-fedid/digital-credentials#481.
-
editorial: link defined terms and fix broken dfn scope w3c-fedid/digital-credentials#507.
-
-
10 pull requests received 42 new comments.
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381 (28 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
editorial: Terminology Updates w3c-fedid/digital-credentials#516 (4 comments by @marcoscaceres, @timcappalli)
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520 (2 comments by @marcoscaceres, @mohamedamir)
-
Replace mediation "MUST NOT throw" prose with [[implicitMediation]] slot w3c-fedid/digital-credentials#511 (2 comments by @marcoscaceres, @TallTed)
-
w3c-fedid/digital-credentials#521 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#518 (1 comment by @w3cbot)
-
Remove "origin bound" declaration from DigitalCredential w3c-fedid/digital-credentials#509 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#513 (1 comment by @w3cbot)
-
Clarify network and protocol tampering threats w3c-fedid/digital-credentials#493 (1 comment by @TallTed)
-
Add API Flooding security considerations w3c-fedid/digital-credentials#481 (1 comment by @mohamedamir)
-
w3c-fedid/FedCM
-
3 issues opened.
-
Remaining items to resolve in IDP Service Worker design w3c-fedid/FedCM#833, by @domfarolino.
-
Clarify fallback vs failure behavior in sub-domain well-known discovery w3c-fedid/FedCM#832, by @pottis.
-
Standards compliance concerns raised by Dominic in Spec w3c-fedid/FedCM#829, by @pottis.
-
-
8 issues received 27 new comments.
-
Remaining items to resolve in IDP Service Worker design w3c-fedid/FedCM#833 (14 comments by @domfarolino, @pottis, @wanderview, @yoshisatoyanagisawa)
-
Standards compliance concerns raised by Dominic in Spec w3c-fedid/FedCM#829 (4 comments by @domfarolino, @samuelgoto, @TallTed)
-
FedCM facilitates vendor lock-in w3c-fedid/FedCM#827 (4 comments by @hlflanagan, @will-bartlett, @wparad)
-
w3c-fedid/FedCM#29 (1 comment by @hlflanagan)
-
Discovery of Token Validation Metadata and Protocol Binding w3c-fedid/FedCM#810 (1 comment by @hlflanagan)
-
-
3 pull requests opened.
-
Explainer for IDP interception via Service Worker w3c-fedid/FedCM#831, by @pottis.
-
Explainer for IDP interception via Service Worker w3c-fedid/FedCM#830, by @pottis.
-
Explainer for FedCM well-known subdomain discovery w3c-fedid/FedCM#828, by @pottis.
-
-
3 pull requests merged.
-
Explainer for IDP interception via Service Worker w3c-fedid/FedCM#831.
-
Explainer for IDP interception via Service Worker w3c-fedid/FedCM#830.
-
Explainer for FedCM well-known subdomain discovery w3c-fedid/FedCM#828.
-
-
3 pull requests received 74 new comments.
-
Enabling IDP Interception in FedCM Request w3c-fedid/FedCM#815 (66 comments by @domfarolino, @hlflanagan, @monica-ch, @pottis, @TallTed, @wanderview, @yoshisatoyanagisawa)
-
Allow IDPs to host well-known file at web-identity. subdomain w3c-fedid/FedCM#823 (7 comments by @TallTed)
-
Allow IDPs to delegate well-known file hosting via DNS TXT record w3c-fedid/FedCM#821 (1 comment by @hlflanagan)
-
TR publications
-
7 documents published.
-
Digital Credentials published 7 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
6 meetings.
Participants
-
2 participants joined.
-
Nikos Karapanos (Futurae Technologies AG) joined.
-
Zahra Ebadi Ansaroudi (Fondazione Bruno Kessler) joined.
-
-
1 participant left.
-
Srdjan Marinvoic (Futurae Technologies AG) left.
-
-
1 organization joined.
-
Fondazione Bruno Kessler joined.
-
GitHub
w3c-fedid/FedCM
-
4 issues opened.
-
FedCM facilitates vendor lock-in w3c-fedid/FedCM#827, by @will-bartlett.
-
Support moving endpoints gradually w3c-fedid/FedCM#826, by @will-bartlett.
-
Cookie headers in examples are incorrect w3c-fedid/FedCM#825, by @ThisIsMissEm.
-
Which cookies are sent with FedCM requests? w3c-fedid/FedCM#824, by @ThisIsMissEm.
-
-
4 issues received 19 new comments.
-
FedCM facilitates vendor lock-in w3c-fedid/FedCM#827 (14 comments by @cbiesinger, @will-bartlett, @wparad)
-
Which cookies are sent with FedCM requests? w3c-fedid/FedCM#824 (3 comments by @npm1, @ThisIsMissEm, @will-bartlett)
-
-
2 pull requests opened.
-
Allow IDPs to host well-known file at web-identity. subdomain w3c-fedid/FedCM#823, by @will-bartlett.
-
Explainer for IDP interception via Service Worker w3c-fedid/FedCM#822, by @pottis.
-
-
1 pull request merged.
-
Explainer for IDP interception via Service Worker w3c-fedid/FedCM#822.
-
-
1 pull request reopened.
-
Enabling IDP Interception in FedCM Request w3c-fedid/FedCM#815, by @pottis.
-
-
2 pull requests received 181 new comments.
-
Enabling IDP Interception in FedCM Request w3c-fedid/FedCM#815 (131 comments by @cbiesinger, @domfarolino, @hlflanagan, @npm1, @pottis, @samuelgoto, @TallTed, @yoshisatoyanagisawa)
-
Allow IDPs to delegate well-known file hosting via DNS TXT record w3c-fedid/FedCM#821 (50 comments by @bemasc, @hlflanagan, @npm1, @samuelgoto, @TallTed, @will-bartlett)
-
w3c-fedid/digital-credentials
-
6 issues opened.
-
Include the requesting document's origin in the request context w3c-fedid/digital-credentials#504, by @marcoscaceres.
-
Add testing action to simulate platform error mapping in the "present" algorithm w3c-fedid/digital-credentials#500, by @mohamedamir.
-
Support testing of response parsing and validation failures in Virtual Wallet automation w3c-fedid/digital-credentials#498, by @mohamedamir.
-
IPIADDRESS.COM w3c-fedid/digital-credentials#497, by @atlassians.
-
Rate limiting: implementer considerations w3c-fedid/digital-credentials#495, by @marcoscaceres.
-
Protocol Integrity Requirements for Request/Response Tampering w3c-fedid/digital-credentials#494, by @simoneonofri.
-
-
8 issues closed.
-
Manage abort signal's lifecycle w3c-fedid/digital-credentials#460.
-
Explain how userAgentAllowsProtocol future proofs the API w3c-fedid/digital-credentials#470.
-
IPIADDRESS.COM w3c-fedid/digital-credentials#497.
-
Inconsistencies between request data & issuance request data w3c-fedid/digital-credentials#482.
-
Publish and link the Threat Model for Digital Credentials API w3c-fedid/digital-credentials#440.
-
Canonical test objects for OpenID4VP and Openid4VCI w3c-fedid/digital-credentials#433.
-
Transport-only model with delegated behavior... API w3c-fedid/digital-credentials#489.
-
Revise introduction and abstract w3c-fedid/digital-credentials#361.
-
-
3 issues reopened.
-
IPIADDRESS.COM w3c-fedid/digital-credentials#497, by @mohamedamir.
-
Publish and link the Threat Model for Digital Credentials API w3c-fedid/digital-credentials#440, by @marcoscaceres.
-
Adding Signature as Response for Tampering and consider Encryption w3c-fedid/digital-credentials#479, by @simoneonofri.
-
-
27 issues received 38 new comments.
-
Protocol Integrity Requirements for Request/Response Tampering w3c-fedid/digital-credentials#494 (3 comments by @hlflanagan, @npdoty)
-
Transport-only model with delegated behavior... API w3c-fedid/digital-credentials#489 (3 comments by @hlflanagan, @marcoscaceres)
-
Publish and link the Threat Model for Digital Credentials API w3c-fedid/digital-credentials#440 (2 comments by @marcoscaceres)
-
Proposal: Relax transient user activation requirement for all DC API requests w3c-fedid/digital-credentials#478 (2 comments by @hlflanagan, @jschanck)
-
user agents should limit to protocols listed in the registry that meet the group's requirements w3c-fedid/digital-credentials#288 (1 comment by @marcoscaceres)
-
The digital credential definition should include "verifiable" aspect w3c-fedid/digital-credentials#198 (1 comment by @marcoscaceres)
-
Most users will experience a no-matching-credential dead-end w3c-fedid/digital-credentials#104 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#84 (1 comment by @marcoscaceres)
-
Threat Modeling for Decentralized Identities w3c-fedid/digital-credentials#115 (1 comment by @marcoscaceres)
-
Tradeoffs of being more or less conservative in DC API velocity w3c-fedid/digital-credentials#106 (1 comment by @marcoscaceres)
-
Choice of issuers and consequent exclusion risk w3c-fedid/digital-credentials#298 (1 comment by @marcoscaceres)
-
define consent and permission; explain split roles regarding consent w3c-fedid/digital-credentials#290 (1 comment by @marcoscaceres)
-
note designed-for-purpose alternatives and the risk of crowding out those options w3c-fedid/digital-credentials#289 (1 comment by @marcoscaceres)
-
Privacy Considerations: Preventing information leakage and fingerprinting w3c-fedid/digital-credentials#245 (1 comment by @marcoscaceres)
-
Privacy Considerations: Addressing "unnecessary" usage of the API w3c-fedid/digital-credentials#243 (1 comment by @marcoscaceres)
-
Privacy Considerations: "Spectrum of Privacy" w3c-fedid/digital-credentials#242 (1 comment by @marcoscaceres)
-
Access to an Open Global Web Reduced w3c-fedid/digital-credentials#123 (1 comment by @marcoscaceres)
-
Should response encryption be required w3c-fedid/digital-credentials#109 (1 comment by @marcoscaceres)
-
Privacy: ensuring RPs blinded to credential existence w3c-fedid/digital-credentials#105 (1 comment by @marcoscaceres)
-
Include the requesting document's origin in the request context w3c-fedid/digital-credentials#504 (1 comment by @timcappalli)
-
Canonical test objects for OpenID4VP and Openid4VCI w3c-fedid/digital-credentials#433 (1 comment by @marcoscaceres)
-
Privacy review of the supported presentation protocols w3c-fedid/digital-credentials#226 (1 comment by @hlflanagan)
-
8 pull requests opened.
-
editorial: link defined terms and fix broken dfn scope w3c-fedid/digital-credentials#507, by @marcoscaceres.
-
Add security considerations on forged credential chooser requests w3c-fedid/digital-credentials#506, by @marcoscaceres.
-
editorial: fix closure capture, parameter type, and grammar w3c-fedid/digital-credentials#505, by @marcoscaceres.
-
chore: move .github/AGENTS.md to .github/instructions/html.instructions.md w3c-fedid/digital-credentials#503, by @marcoscaceres.
-
chore: use ReSpec v36 CDDL inline references w3c-fedid/digital-credentials#502, by @marcoscaceres.
-
editorial: remove threat model issue marker and fix stale reference w3c-fedid/digital-credentials#496, by @marcoscaceres.
-
Clarify network and protocol tampering threats w3c-fedid/digital-credentials#493, by @simoneonofri.
-
Simplify and clarify core algorithms w3c-fedid/digital-credentials#491, by @marcoscaceres.
-
-
10 pull requests merged.
-
Define "present credential requests" algorithm. w3c-fedid/digital-credentials#419.
-
chore: move .github/AGENTS.md to .github/instructions/html.instructions.md w3c-fedid/digital-credentials#503.
-
chore: use ReSpec v36 CDDL inline references w3c-fedid/digital-credentials#502.
-
editorial: explain how userAgentAllowsProtocol() future-proofs the API w3c-fedid/digital-credentials#484.
-
Simplify and clarify core algorithms w3c-fedid/digital-credentials#491.
-
Editorial: rename "Request data" to "Presentation request data" w3c-fedid/digital-credentials#483.
-
editorial: remove threat model issue marker and fix stale reference w3c-fedid/digital-credentials#496.
-
Adding Signature as Response for Tampering w3c-fedid/digital-credentials#487.
-
Add Unauthorized Cross-Origin Access and mitigation w3c-fedid/digital-credentials#480.
-
editorial: revise abstract and introduction w3c-fedid/digital-credentials#485.
-
-
15 pull requests received 99 new comments.
-
Define "present credential requests" algorithm. w3c-fedid/digital-credentials#419 (26 comments by @hlflanagan, @marcoscaceres, @mohamedamir, @TallTed, @wseltzer)
-
Adding Signature as Response for Tampering w3c-fedid/digital-credentials#487 (18 comments by @marcoscaceres, @simoneonofri, @TallTed)
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381 (12 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
Simplify and clarify core algorithms w3c-fedid/digital-credentials#491 (10 comments by @marcoscaceres, @TallTed)
-
editorial: explain how userAgentAllowsProtocol() future-proofs the API w3c-fedid/digital-credentials#484 (6 comments by @marcoscaceres, @TallTed)
-
Add API Flooding security considerations w3c-fedid/digital-credentials#481 (5 comments by @marcoscaceres, @mohamedamir, @timcappalli)
-
Add Unauthorized Cross-Origin Access and mitigation w3c-fedid/digital-credentials#480 (5 comments by @hlflanagan, @marcoscaceres)
-
Relax transient activation requirement for DC API requests w3c-fedid/digital-credentials#486 (4 comments by @hlflanagan, @npdoty, @TallTed)
-
Editorial: rename "Request data" to "Presentation request data" w3c-fedid/digital-credentials#483 (4 comments by @marcoscaceres, @TallTed)
-
Clarify network and protocol tampering threats w3c-fedid/digital-credentials#493 (3 comments by @marcoscaceres, @TallTed, @timcappalli)
-
Require support for all presentation protocols w3c-fedid/digital-credentials#454 (2 comments by @marcoscaceres, @TallTed)
-
w3c-fedid/digital-credentials#501 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#499 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#492 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#490 (1 comment by @w3cbot)
-
TR publications
-
4 documents published.
-
Digital Credentials published 4 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
6 meetings.
Participants
-
2 participants joined.
-
John Schanck (Mozilla Foundation) joined.
-
Dmitri Zagidulin (W3C Invited Experts) joined.
-
GitHub
w3c-fedid/digital-credentials
-
8 issues opened.
-
Transport-only model with delegated behavior... API w3c-fedid/digital-credentials#489, by @simoneonofri.
-
Inconsistencies between request data & issuance request data w3c-fedid/digital-credentials#482, by @c2bo.
-
Adding Signature as Response for Tampering and consider Encryption w3c-fedid/digital-credentials#479, by @simoneonofri.
-
Proposal: Relax transient user activation requirement for all DC API requests w3c-fedid/digital-credentials#478, by @mohamedamir.
-
Order of serialization vs protocol filtering w3c-fedid/digital-credentials#475, by @marcoscaceres.
-
User agent request validation and errors w3c-fedid/digital-credentials#472, by @marcoscaceres.
-
EUDI Wallet functional conformance testing w3c-fedid/digital-credentials#471, by @simoneonofri.
-
Explain how userAgentAllowsProtocol future proofs the API w3c-fedid/digital-credentials#470, by @marcoscaceres.
-
-
7 issues closed.
-
Order of serialization vs protocol filtering w3c-fedid/digital-credentials#475.
-
Security considerations don't relate directly to the spec w3c-fedid/digital-credentials#346.
-
Handling ongoing operations / subsequent call to get() w3c-fedid/digital-credentials#159.
-
Issuance: multiple requests w3c-fedid/digital-credentials#207.
-
Support for multiple requests in a get call w3c-fedid/digital-credentials#220.
-
Update get procedure for when UA does not support a protocol w3c-fedid/digital-credentials#432.
-
Describe what happens when execution context is destroyed w3c-fedid/digital-credentials#435.
-
-
1 issue reopened.
-
Proposal: Relax transient user activation requirement for all DC API requests w3c-fedid/digital-credentials#478, by @mohamedamir.
-
-
10 issues received 29 new comments.
-
Order of serialization vs protocol filtering w3c-fedid/digital-credentials#475 (6 comments by @c2bo, @hlflanagan, @marcoscaceres, @mohamedamir, @timcappalli)
-
Transport-only model with delegated behavior... API w3c-fedid/digital-credentials#489 (5 comments by @jandrieu, @marcoscaceres, @simoneonofri, @timcappalli)
-
EUDI Wallet functional conformance testing w3c-fedid/digital-credentials#471 (5 comments by @awoie, @hlflanagan, @marcoscaceres, @simoneonofri)
-
User agent request validation and errors w3c-fedid/digital-credentials#472 (4 comments by @marcoscaceres, @timcappalli)
-
Wallet Selection Binding during Issuance w3c-fedid/digital-credentials#382 (3 comments by @hlozi, @marcoscaceres, @wseltzer)
-
Proposal: Relax transient user activation requirement for all DC API requests w3c-fedid/digital-credentials#478 (2 comments by @marcoscaceres, @mohamedamir)
-
Security considerations don't relate directly to the spec w3c-fedid/digital-credentials#346 (1 comment by @marcoscaceres)
-
Inconsistencies between request data & issuance request data w3c-fedid/digital-credentials#482 (1 comment by @marcoscaceres)
-
Linkability and issuer involvement as a protocol requirement w3c-fedid/digital-credentials#279 (1 comment by @npdoty)
-
Privacy review of the supported presentation protocols w3c-fedid/digital-credentials#226 (1 comment by @npdoty)
-
-
11 pull requests opened.
-
chore: add .gitattributes to enforce LF line endings w3c-fedid/digital-credentials#488, by @marcoscaceres.
-
Adding Signature as Response for Tampering w3c-fedid/digital-credentials#487, by @simoneonofri.
-
Relax transient activation requirement for DC API requests w3c-fedid/digital-credentials#486, by @mohamedamir.
-
editorial: revise abstract and introduction w3c-fedid/digital-credentials#485, by @marcoscaceres.
-
editorial: explain how userAgentAllowsProtocol() future-proofs the API w3c-fedid/digital-credentials#484, by @marcoscaceres.
-
Editorial: rename "Request data" to "Presentation request data" w3c-fedid/digital-credentials#483, by @marcoscaceres.
-
Add API Flooding security considerations w3c-fedid/digital-credentials#481, by @marcoscaceres.
-
Add Unauthorized Cross-Origin Access and mitigation w3c-fedid/digital-credentials#480, by @marcoscaceres.
-
Address order of serialization vs protocol filtering (issue #475) w3c-fedid/digital-credentials#477, by @mohamedamir.
-
Editorial: Fix capitalization and some minor editorial tweaks w3c-fedid/digital-credentials#476, by @mohamedamir.
-
All requests must go to client platform for cross-device w3c-fedid/digital-credentials#474, by @timcappalli.
-
-
6 pull requests merged.
-
chore: add .gitattributes to enforce LF line endings w3c-fedid/digital-credentials#488.
-
Address order of serialization vs protocol filtering (issue #475) w3c-fedid/digital-credentials#477.
-
Addressing Request Tampering w3c-fedid/digital-credentials#426.
-
Editorial: Fix capitalization and some minor editorial tweaks w3c-fedid/digital-credentials#476.
-
Define "prepare credential requests" algorithm w3c-fedid/digital-credentials#420.
-
Add "Abort the credential request" algorithm w3c-fedid/digital-credentials#462.
-
-
15 pull requests received 173 new comments.
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381 (48 comments by @marcoscaceres, @mohamedamir, @TallTed, @tidoust, @whimboo)
-
Define "prepare credential requests" algorithm w3c-fedid/digital-credentials#420 (31 comments by @marcoscaceres, @mohamedamir, @TallTed, @timcappalli, @wseltzer)
-
Addressing Request Tampering w3c-fedid/digital-credentials#426 (20 comments by @c2bo, @dlongley, @hlflanagan, @marcoscaceres, @mikewest, @simoneonofri, @TallTed, @wseltzer)
-
Adding Signature as Response for Tampering w3c-fedid/digital-credentials#487 (17 comments by @anowardear062-svg, @marcoscaceres, @mohamedamir, @simoneonofri, @TallTed)
-
Add API Flooding security considerations w3c-fedid/digital-credentials#481 (13 comments by @hlflanagan, @marcoscaceres, @simoneonofri, @TallTed)
-
All requests must go to client platform for cross-device w3c-fedid/digital-credentials#474 (11 comments by @c2bo, @dlongley, @marcoscaceres, @mohamedamir, @TallTed)
-
Add Unauthorized Cross-Origin Access and mitigation w3c-fedid/digital-credentials#480 (8 comments by @hlflanagan, @marcoscaceres, @simoneonofri, @TallTed)
-
Address order of serialization vs protocol filtering (issue #475) w3c-fedid/digital-credentials#477 (8 comments by @marcoscaceres, @mohamedamir)
-
Relax transient activation requirement for DC API requests w3c-fedid/digital-credentials#486 (7 comments by @marcoscaceres)
-
editorial: revise abstract and introduction w3c-fedid/digital-credentials#485 (3 comments by @TallTed)
-
Editorial: rename "Request data" to "Presentation request data" w3c-fedid/digital-credentials#483 (2 comments by @c2bo, @marcoscaceres)
-
Add "Abort the credential request" algorithm w3c-fedid/digital-credentials#462 (2 comments by @marcoscaceres, @wseltzer)
-
Editorial: Fix capitalization and some minor editorial tweaks w3c-fedid/digital-credentials#476 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#473 (1 comment by @w3cbot)
-
Define "present credential requests" algorithm. w3c-fedid/digital-credentials#419 (1 comment by @TallTed)
-
w3c-fedid/FedCM
-
5 issues opened.
-
DPoP for FedCM (natively) w3c-fedid/FedCM#820, by @ThisIsMissEm.
-
Usability/UX/Accessability Research? w3c-fedid/FedCM#819, by @blaine.
-
Should this be 10 seconds? Or, it is fine for each implementation to decide? w3c-fedid/FedCM#818, by @lardinroselia932-lab.
-
Cross-device/System-level FedCM Flows? w3c-fedid/FedCM#817, by @ThisIsMissEm.
-
storage red w3c-fedid/FedCM#816, by @joemherdezz.
-
-
2 issues closed.
-
Should this be 10 seconds? Or, it is fine for each implementation to decide? w3c-fedid/FedCM#818.
-
storage red w3c-fedid/FedCM#816.
-
-
5 issues received 20 new comments.
-
Cross-device/System-level FedCM Flows? w3c-fedid/FedCM#817 (11 comments by @EmLauber, @samuelgoto, @ThisIsMissEm, @will-bartlett, @wseltzer)
-
Enterprise Scenarios: admin consent for users w3c-fedid/FedCM#715 (2 comments by @ThisIsMissEm, @will-bartlett)
-
w3c-fedid/FedCM#435 (1 comment by @rabbima)
-
-
1 pull request opened.
-
Allow IDPs to delegate well-known file hosting via DNS TXT record w3c-fedid/FedCM#821, by @will-bartlett.
-
-
1 pull request closed.
-
Update service-workers mode to all for credentialed requests w3c-fedid/FedCM#787.
-
-
3 pull requests received 141 new comments.
-
Enabling IDP Interception in FedCM Request w3c-fedid/FedCM#815 (116 comments by @domfarolino, @pottis, @TallTed, @wseltzer, @yoshisatoyanagisawa)
-
Allow IDPs to delegate well-known file hosting via DNS TXT record w3c-fedid/FedCM#821 (24 comments by @samuelgoto, @ThisIsMissEm, @will-bartlett)
-
Update service-workers mode to all for credentialed requests w3c-fedid/FedCM#787 (1 comment by @will-bartlett)
-
TR publications
-
5 documents published.
-
Digital Credentials published 5 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
5 meetings.
Participants
-
2 participants joined.
-
Emelia Smith (W3C Invited Experts) joined.
-
Jonathan Prisby (Department of Homeland Security) joined.
-
-
1 participant left.
-
Anil John (Department of Homeland Security) left.
-
GitHub
w3c-fedid/FedCM
-
3 issues opened.
-
surinhemonto@gmail.com w3c-fedid/FedCM#812, by @shemonto426-cmd.
-
Discovery of Token Validation Metadata and Protocol Binding w3c-fedid/FedCM#810, by @oroka750.
-
-
3 issues closed.
-
surinhemonto@gmail.com w3c-fedid/FedCM#812.
-
J w3c-fedid/FedCM#808.
-
Hi w3c-fedid/FedCM#807.
-
-
3 issues received 22 new comments.
-
Use of apex domain is hard for organizations with different services owning different subdomains w3c-fedid/FedCM#809 (11 comments by @hlflanagan, @mooreds, @npm1, @samuelgoto, @TallTed, @will-bartlett)
-
Discovery of Token Validation Metadata and Protocol Binding w3c-fedid/FedCM#810 (10 comments by @aaronpk, @hlflanagan, @npm1, @oroka750, @samuelgoto)
-
w3c-fedid/FedCM#441 (1 comment by @hlflanagan)
-
-
3 pull requests opened.
-
Enabling IDP Interception in FedCM Request w3c-fedid/FedCM#815, by @pottis.
-
add support for IDP to intercept fedcm request vis service worker w3c-fedid/FedCM#814, by @pottis.
-
Add new editor Emily Lauber to index.bs w3c-fedid/FedCM#813, by @npm1.
-
-
3 pull requests merged.
-
Add new editor Emily Lauber to index.bs w3c-fedid/FedCM#813.
-
FedCM Service Worker Interception w3c-fedid/FedCM#802.
-
Move Navigation Interception API document to new location w3c-fedid/FedCM#806.
-
-
2 pull requests closed.
-
add support for IDP to intercept fedcm request vis service worker w3c-fedid/FedCM#814.
-
Convert required email field in user account to optional w3c-fedid/FedCM#433.
-
-
4 pull requests received 81 new comments.
-
FedCM Service Worker Interception w3c-fedid/FedCM#802 (77 comments by @cbiesinger, @npm1, @pottis, @TallTed)
-
add support for IDP to intercept fedcm request vis service worker w3c-fedid/FedCM#814 (1 comment by @pottis)
-
w3c-fedid/digital-credentials
-
3 issues opened.
-
Manage abort signal's lifecycle w3c-fedid/digital-credentials#460, by @marcoscaceres.
-
Error from "complete credential request with error" could be in wrong realm w3c-fedid/digital-credentials#457, by @marcoscaceres.
-
Presenting with CTAP w3c-fedid/digital-credentials#456, by @marcoscaceres.
-
-
5 issues closed.
-
Add OPENID4VCI to the Protocols w3c-fedid/digital-credentials#453.
-
Security considerations needs an intro and some structure w3c-fedid/digital-credentials#438.
-
Error from "complete credential request with error" could be in wrong realm w3c-fedid/digital-credentials#457.
-
Add typedef and change `DigitalCredential` `protocol` type w3c-fedid/digital-credentials#441.
-
Protocols table hard to read/use on mobile w3c-fedid/digital-credentials#450.
-
-
8 issues received 22 new comments.
-
Presenting with CTAP w3c-fedid/digital-credentials#456 (6 comments by @hlflanagan, @marcoscaceres, @mohamedamir, @timcappalli)
-
Privacy review of the supported presentation protocols w3c-fedid/digital-credentials#226 (5 comments by @gffletch, @hlflanagan, @npdoty)
-
Add OPENID4VCI to the Protocols w3c-fedid/digital-credentials#453 (4 comments by @jogu, @marcoscaceres, @mohamedamir, @timcappalli)
-
Define concrete privacy and security requirements for the supported protocols w3c-fedid/digital-credentials#255 (2 comments by @hlflanagan)
-
What protocols should a user agent implement? w3c-fedid/digital-credentials#439 (2 comments by @hlflanagan, @marcoscaceres)
-
Create an issue template for registration w3c-fedid/digital-credentials#223 (1 comment by @marcoscaceres)
-
Should we normatively define elements of a permission prompt? w3c-fedid/digital-credentials#252 (1 comment by @marcoscaceres)
-
Canonical test objects for OpenID4VP and Openid4VCI w3c-fedid/digital-credentials#433 (1 comment by @jogu)
-
-
7 pull requests opened.
-
Editorial: restructure Security Considerations w3c-fedid/digital-credentials#468, by @marcoscaceres.
-
Add openid4vci-v1 issuance protocol and enumeration w3c-fedid/digital-credentials#465, by @mohamedamir.
-
Editorial: fix typo DigitalCredentialsProtocol -> DigitalCredentialProtocol w3c-fedid/digital-credentials#464, by @marcoscaceres.
-
Add slots for abort management w3c-fedid/digital-credentials#463, by @marcoscaceres.
-
Add "Abort the credential request" algorithm w3c-fedid/digital-credentials#462, by @marcoscaceres.
-
Add algorithm signature for 'prepare credential requests' w3c-fedid/digital-credentials#461, by @marcoscaceres.
-
Complete credential request in promise's realm w3c-fedid/digital-credentials#458, by @marcoscaceres.
-
-
9 pull requests merged.
-
Add slots for abort management w3c-fedid/digital-credentials#463.
-
Add algorithm signature for 'prepare credential requests' w3c-fedid/digital-credentials#461.
-
Editorial: restructure Security Considerations w3c-fedid/digital-credentials#468.
-
Add openid4vci-v1 issuance protocol and enumeration w3c-fedid/digital-credentials#465.
-
Editorial: Add structure and Introduction to Security Considerations w3c-fedid/digital-credentials#424.
-
Complete credential request in promise's realm w3c-fedid/digital-credentials#458.
-
Editorial: fix typo DigitalCredentialsProtocol -> DigitalCredentialProtocol w3c-fedid/digital-credentials#464.
-
Add 'DigitalCredentialProtocol' typedef w3c-fedid/digital-credentials#452.
-
Editorial: fixup protocol table + make mobile friendly w3c-fedid/digital-credentials#451.
-
-
8 pull requests closed.
-
Security Considerations: Permission Policy w3c-fedid/digital-credentials#427.
-
Security Considerations: Error Messages Normalization w3c-fedid/digital-credentials#430.
-
Security Considerations: Origin Verification and Expected-Origins Sig… w3c-fedid/digital-credentials#429.
-
Security Considerations: User Activation and User Mediation w3c-fedid/digital-credentials#428.
-
Security Considerations: In-Scope and Out-of-Scope Threats w3c-fedid/digital-credentials#425.
-
Use SecurityError for document state check w3c-fedid/digital-credentials#143.
-
Security Considerations: Writing first round of threats and mitigatio… w3c-fedid/digital-credentials#277.
-
Editorial: Protocols fixup w3c-fedid/digital-credentials#443.
-
-
23 pull requests received 127 new comments.
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381 (34 comments by @burg, @marcoscaceres, @mohamedamir, @sadym-chromium, @whimboo)
-
Define "prepare credential requests" algorithm w3c-fedid/digital-credentials#420 (12 comments by @marcoscaceres, @mohamedamir)
-
Add openid4vci-v1 issuance protocol and enumeration w3c-fedid/digital-credentials#465 (11 comments by @hlflanagan, @marcoscaceres, @mohamedamir, @TallTed)
-
Add "Abort the credential request" algorithm w3c-fedid/digital-credentials#462 (10 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
Require support for all presentation protocols w3c-fedid/digital-credentials#454 (9 comments by @hlflanagan, @marcoscaceres, @npdoty, @TallTed)
-
Editorial: Add structure and Introduction to Security Considerations w3c-fedid/digital-credentials#424 (9 comments by @hlflanagan, @marcoscaceres, @mohamedamir, @simoneonofri, @TallTed)
-
Addressing Request Tampering w3c-fedid/digital-credentials#426 (7 comments by @c2bo, @hlflanagan, @marcoscaceres, @npdoty, @simoneonofri)
-
Define "present credential requests" algorithm. w3c-fedid/digital-credentials#419 (7 comments by @hlflanagan, @marcoscaceres)
-
Add slots for abort management w3c-fedid/digital-credentials#463 (7 comments by @marcoscaceres, @mohamedamir)
-
Add algorithm signature for 'prepare credential requests' w3c-fedid/digital-credentials#461 (6 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
Security Considerations: Error Messages Normalization w3c-fedid/digital-credentials#430 (2 comments by @simoneonofri)
-
Security Considerations: In-Scope and Out-of-Scope Threats w3c-fedid/digital-credentials#425 (2 comments by @kdenhartog, @simoneonofri)
-
Security Considerations: Permission Policy w3c-fedid/digital-credentials#427 (1 comment by @simoneonofri)
-
Security Considerations: Origin Verification and Expected-Origins Sig… w3c-fedid/digital-credentials#429 (1 comment by @simoneonofri)
-
Security Considerations: User Activation and User Mediation w3c-fedid/digital-credentials#428 (1 comment by @simoneonofri)
-
w3c-fedid/digital-credentials#469 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#467 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#466 (1 comment by @w3cbot)
-
Complete credential request in promise's realm w3c-fedid/digital-credentials#458 (1 comment by @mohamedamir)
-
Editorial: fixup protocol table + make mobile friendly w3c-fedid/digital-credentials#451 (1 comment by @marcoscaceres)
-
Use SecurityError for document state check w3c-fedid/digital-credentials#143 (1 comment by @marcoscaceres)
-
Security Considerations: Writing first round of threats and mitigatio… w3c-fedid/digital-credentials#277 (1 comment by @marcoscaceres)
-
TR publications
-
5 documents published.
-
Digital Credentials published 5 times as a Working Draft. History of Digital Credentials
-
Past meetings
Participants
-
2 participants joined.
-
Michael Animashaun (HM Government) joined.
-
Chandana Sathish (1Password) joined.
-
-
2 participants left.
-
JP Hribovsek (Apple Inc.) left.
-
Albert Schibani (Capital One Discover Network) left.
-
-
1 organization joined.
-
HM Government joined.
-
GitHub
w3c-fedid/FedCM
-
7 issues opened.
-
J w3c-fedid/FedCM#808, by @ssoe65111-debug.
-
Hi w3c-fedid/FedCM#807, by @ssoe65111-debug.
-
Zeynep Hamdo w3c-fedid/FedCM#805, by @Dangerous213.
-
bdrindyhx@gmail.com w3c-fedid/FedCM#804, by @Dangerous213.
-
آبًوٌ آلـ,ـجـ,ـۅډ}---♡✓ w3c-fedid/FedCM#803, by @Dangerous213.
-
Dev w3c-fedid/FedCM#801, by @eelcinz1-source.
-
-
5 issues closed.
-
Zeynep Hamdo w3c-fedid/FedCM#805.
-
bdrindyhx@gmail.com w3c-fedid/FedCM#804.
-
آبًوٌ آلـ,ـجـ,ـۅډ}---♡✓ w3c-fedid/FedCM#803.
-
Dev w3c-fedid/FedCM#801.
-
-
3 pull requests opened.
-
Move Navigation Interception API document to new location w3c-fedid/FedCM#806, by @samuelgoto.
-
FedCM Service Worker Interception w3c-fedid/FedCM#802, by @pottis.
-
Revise problem statement for Navigation Interception API w3c-fedid/FedCM#799, by @samuelgoto.
-
-
1 pull request merged.
-
Revise problem statement for Navigation Interception API w3c-fedid/FedCM#799.
-
-
4 pull requests received 42 new comments.
-
FedCM Service Worker Interception w3c-fedid/FedCM#802 (31 comments by @hlflanagan, @npm1, @pottis, @samuelgoto)
-
Update service-workers mode to all for credentialed requests w3c-fedid/FedCM#787 (7 comments by @cbiesinger, @domfarolino, @samuelgoto, @will-bartlett)
-
Revise problem statement for Navigation Interception API w3c-fedid/FedCM#799 (2 comments by @TallTed)
-
w3c-fedid/FedCM#208 (2 comments by @eddielong652-netizen)
-
w3c-fedid/digital-credentials
-
10 issues opened.
-
Add OPENID4VCI to the Protocols w3c-fedid/digital-credentials#453, by @marcoscaceres.
-
Protocols table hard to read/use on mobile w3c-fedid/digital-credentials#450, by @marcoscaceres.
-
Add typedef and change `DigitalCredential` `protocol` type w3c-fedid/digital-credentials#441, by @timcappalli.
-
Publish and link the Threat Model for Digital Credentials API w3c-fedid/digital-credentials#440, by @simoneonofri.
-
What protocols should a user agent implement? w3c-fedid/digital-credentials#439, by @marcoscaceres.
-
Security considerations needs an intro and some structure w3c-fedid/digital-credentials#438, by @marcoscaceres.
-
Describe what happens when execution context is destroyed w3c-fedid/digital-credentials#435, by @marcoscaceres.
-
Drop "exchange protocol" and add "presentation protocol" w3c-fedid/digital-credentials#434, by @timcappalli.
-
Canonical test objects for OpenID4VP and Openid4VCI w3c-fedid/digital-credentials#433, by @marcoscaceres.
-
Update get procedure for when UA does not support a protocol w3c-fedid/digital-credentials#432, by @timcappalli.
-
-
17 issues closed.
-
Drop "exchange protocol" and add "presentation protocol" w3c-fedid/digital-credentials#434.
-
Add examples of usage in registry w3c-fedid/digital-credentials#69.
-
Describe trust signals in protocol registry w3c-fedid/digital-credentials#136.
-
Add OpenID for Verifiable Presentations (OpenID4VP) to registry w3c-fedid/digital-credentials#211.
-
Add OpenID for Verifiable Credential Issuance (OpenID4VCI) to registry w3c-fedid/digital-credentials#212.
-
Add ISO/IEC 18013-7 Annex C to protocol registry w3c-fedid/digital-credentials#213.
-
[Registry] Re-evaluate "freely available" requirement w3c-fedid/digital-credentials#214.
-
Document WG security review requirements for protocols w3c-fedid/digital-credentials#215.
-
Registry requirements should not use RFC2119 language w3c-fedid/digital-credentials#240.
-
Protocol registry: royalty free requirement w3c-fedid/digital-credentials#256.
-
Protocol registry: specification availability w3c-fedid/digital-credentials#257.
-
Is a registry needed? w3c-fedid/digital-credentials#345.
-
Paths towards resolution on the registry [TPAC] w3c-fedid/digital-credentials#396.
-
Requests' size should be checked before transient activation w3c-fedid/digital-credentials#202.
-
Redo security considerations w3c-fedid/digital-credentials#360.
-
Add error for when the API is supported, but the platform doesn't support it w3c-fedid/digital-credentials#359.
-
Clarify what to do when issuance or presentation is not supported w3c-fedid/digital-credentials#393.
-
-
8 issues received 21 new comments.
-
Drop "exchange protocol" and add "presentation protocol" w3c-fedid/digital-credentials#434 (6 comments by @dlongley, @hlflanagan, @marcoscaceres, @timcappalli)
-
What protocols should a user agent implement? w3c-fedid/digital-credentials#439 (3 comments by @MasterKale, @mohamedamir, @timcappalli)
-
Update get procedure for when UA does not support a protocol w3c-fedid/digital-credentials#432 (3 comments by @marcoscaceres, @MasterKale, @timcappalli)
-
Add OPENID4VCI to the Protocols w3c-fedid/digital-credentials#453 (2 comments by @marcoscaceres, @timcappalli)
-
Ensure that credential issuers do not discriminate based on the user’s device or OS w3c-fedid/digital-credentials#349 (2 comments by @DemiMarie, @kdenhartog)
-
[Registry] Re-evaluate "freely available" requirement w3c-fedid/digital-credentials#214 (1 comment by @bc-pi)
-
Canonical test objects for OpenID4VP and Openid4VCI w3c-fedid/digital-credentials#433 (1 comment by @timcappalli)
-
-
18 pull requests opened.
-
Require support for all presentation protocols w3c-fedid/digital-credentials#454, by @marcoscaceres.
-
Add 'DigitalCredentialProtocol' typedef w3c-fedid/digital-credentials#452, by @marcoscaceres.
-
Editorial: fixup protocol table + make mobile friendly w3c-fedid/digital-credentials#451, by @marcoscaceres.
-
Editorial: fix double-code on openid4vp-* dfns w3c-fedid/digital-credentials#449, by @marcoscaceres.
-
Editorial: drop 'supported' from protocol table name w3c-fedid/digital-credentials#448, by @marcoscaceres.
-
Editorial: remove mentions of registry w3c-fedid/digital-credentials#447, by @marcoscaceres.
-
Editorial: fixup small Cred Man integration things w3c-fedid/digital-credentials#445, by @marcoscaceres.
-
Editorial: Protocols fixup w3c-fedid/digital-credentials#443, by @marcoscaceres.
-
Editorial: rename exchange protocol to presentation protocol w3c-fedid/digital-credentials#442, by @marcoscaceres.
-
Restart working on Security Considerations w3c-fedid/digital-credentials#437, by @marcoscaceres.
-
Editorial: return promises instead of throwing exceptions w3c-fedid/digital-credentials#431, by @marcoscaceres.
-
Security Considerations: Error Messages Normalization w3c-fedid/digital-credentials#430, by @simoneonofri.
-
Security Considerations: Origin Verification and Expected-Origins Sig… w3c-fedid/digital-credentials#429, by @simoneonofri.
-
Security Considerations: User Activation and User Mediation w3c-fedid/digital-credentials#428, by @simoneonofri.
-
Security Considerations: Permission Policy w3c-fedid/digital-credentials#427, by @simoneonofri.
-
Addressing Request Tampering w3c-fedid/digital-credentials#426, by @simoneonofri.
-
Security Considerations: In-Scope and Out-of-Scope Threats w3c-fedid/digital-credentials#425, by @simoneonofri.
-
Editorial: Add structure and Introduction to Security Considerations w3c-fedid/digital-credentials#424, by @simoneonofri.
-
-
11 pull requests merged.
-
Editorial: remove mentions of registry w3c-fedid/digital-credentials#447.
-
Editorial: fixup small Cred Man integration things w3c-fedid/digital-credentials#445.
-
Editorial: rename exchange protocol to presentation protocol w3c-fedid/digital-credentials#442.
-
Editorial: fix double-code on openid4vp-* dfns w3c-fedid/digital-credentials#449.
-
Change from Registry to Protocols w3c-fedid/digital-credentials#401.
-
Fixup algorithms in credential creation and request steps. w3c-fedid/digital-credentials#418.
-
Restart working on Security Considerations w3c-fedid/digital-credentials#437.
-
Fallback to Cred Man when the API is not supported w3c-fedid/digital-credentials#395.
-
Editorial: return promises instead of throwing exceptions w3c-fedid/digital-credentials#431.
-
Define "complete credential request with error" w3c-fedid/digital-credentials#421.
-
Introduce "active promise" concept for request coordinator. w3c-fedid/digital-credentials#417.
-
-
3 pull requests closed.
-
Editorial: drop 'supported' from protocol table name w3c-fedid/digital-credentials#448.
-
Add guidance on how to handle multiple presentation request entries w3c-fedid/digital-credentials#249.
-
Security Considerations: Writing Introduction w3c-fedid/digital-credentials#272.
-
-
23 pull requests received 265 new comments.
-
Change from Registry to Protocols w3c-fedid/digital-credentials#401 (116 comments by @bc-pi, @hlflanagan, @marcoscaceres, @MasterKale, @mohamedamir, @RByers, @TallTed, @timcappalli, @wseltzer)
-
Editorial: Add structure and Introduction to Security Considerations w3c-fedid/digital-credentials#424 (48 comments by @marcoscaceres, @mohamedamir, @simoneonofri, @TallTed, @timcappalli)
-
Define "prepare credential requests" algorithm w3c-fedid/digital-credentials#420 (22 comments by @hlflanagan, @jschanck, @marcoscaceres, @mohamedamir)
-
Define "present credential requests" algorithm. w3c-fedid/digital-credentials#419 (21 comments by @hlflanagan, @jschanck, @marcoscaceres, @mohamedamir)
-
Addressing Request Tampering w3c-fedid/digital-credentials#426 (7 comments by @kdenhartog, @TallTed)
-
Editorial: drop 'supported' from protocol table name w3c-fedid/digital-credentials#448 (6 comments by @marcoscaceres, @MasterKale, @timcappalli)
-
Introduce "active promise" concept for request coordinator. w3c-fedid/digital-credentials#417 (5 comments by @marcoscaceres, @mohamedamir, @TallTed)
-
Security Considerations: Origin Verification and Expected-Origins Sig… w3c-fedid/digital-credentials#429 (5 comments by @TallTed, @timcappalli)
-
Fixup algorithms in credential creation and request steps. w3c-fedid/digital-credentials#418 (4 comments by @marcoscaceres)
-
Editorial: return promises instead of throwing exceptions w3c-fedid/digital-credentials#431 (4 comments by @marcoscaceres, @TallTed)
-
Fallback to Cred Man when the API is not supported w3c-fedid/digital-credentials#395 (4 comments by @marcoscaceres, @TallTed)
-
Define "complete credential request with error" w3c-fedid/digital-credentials#421 (4 comments by @marcoscaceres, @mohamedamir)
-
Security Considerations: In-Scope and Out-of-Scope Threats w3c-fedid/digital-credentials#425 (3 comments by @kdenhartog, @simoneonofri, @TallTed)
-
Add guidance on how to handle multiple presentation request entries w3c-fedid/digital-credentials#249 (3 comments by @marcoscaceres, @MasterKale)
-
Editorial: rename exchange protocol to presentation protocol w3c-fedid/digital-credentials#442 (2 comments by @marcoscaceres, @timcappalli)
-
User Agent Automation and WebDriver test support w3c-fedid/digital-credentials#381 (2 comments by @marcoscaceres, @mohamedamir)
-
Require support for all presentation protocols w3c-fedid/digital-credentials#454 (1 comment by @marcoscaceres)
-
Editorial: fixup protocol table + make mobile friendly w3c-fedid/digital-credentials#451 (1 comment by @marcoscaceres)
-
Editorial: fix double-code on openid4vp-* dfns w3c-fedid/digital-credentials#449 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#446 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#436 (1 comment by @w3cbot)
-
Security Considerations: Error Messages Normalization w3c-fedid/digital-credentials#430 (1 comment by @TallTed)
-
w3c-fedid/meetings
-
1 pull request opened.
-
Add FedCM section to agenda w3c-fedid/meetings#5, by @thhck.
-
-
1 pull request closed.
-
Add FedCM section to agenda w3c-fedid/meetings#5.
-