Federated Identity Working Group - Activity
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.
-
Amir Sharif (Fondazione Bruno Kessler) joined.
-
GitHub
w3c-fedid/digital-credentials
-
1 issue opened.
-
Ask HTML to call our unload steps directly w3c-fedid/digital-credentials#607, by @marcoscaceres.
-
-
6 issues closed.
-
Replace "MUST NOT throw" mediation prose with [[implicitMediation]] slot w3c-fedid/digital-credentials#510.
-
Should we normatively define elements of a permission prompt? w3c-fedid/digital-credentials#252.
-
Add guidance to verifiers/issuers and clients/client platforms on cross-origin usage w3c-fedid/digital-credentials#332.
-
Top frame origin should be passed to client platforms and credential managers for cross-origin requests w3c-fedid/digital-credentials#333.
-
Include the requesting document's origin in the request context w3c-fedid/digital-credentials#504.
-
The DC API is unusable on Android devices without Google Play services w3c-fedid/digital-credentials#597, by @dzuluaga.
-
-
8 issues received 10 new comments.
-
The DC API is unusable on Android devices without Google Play services w3c-fedid/digital-credentials#597 (2 comments by @dzuluaga, @marcoscaceres)
-
Privacy review of the supported presentation protocols w3c-fedid/digital-credentials#226 (1 comment by @marcoscaceres)
-
Should requests be assumed to be linkable by the browser? w3c-fedid/digital-credentials#122 (1 comment by @marcoscaceres)
-
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 @marcoscaceres)
-
Prohibit delegating coordinator responsibilities to a credential manager without explicit permission w3c-fedid/digital-credentials#563 (1 comment by @marcoscaceres)
-
Should we normatively define elements of a permission prompt? w3c-fedid/digital-credentials#252 (1 comment by @marcoscaceres)
-
-
6 pull requests opened.
-
Reject with the abort reason if the signal aborts during validation w3c-fedid/digital-credentials#608, by @marcoscaceres.
-
Return the coordinator to idle after the virtual wallet responds or declines w3c-fedid/digital-credentials#606, by @marcoscaceres.
-
Editorial: move the coordinator's reset steps into one algorithm w3c-fedid/digital-credentials#604, by @marcoscaceres.
-
fix: return the coordinator to idle when the requesting document stops being fully active w3c-fedid/digital-credentials#603, by @marcoscaceres.
-
Add privacy considerations on private browsing mode and clearing site data w3c-fedid/digital-credentials#602, by @marcoscaceres.
-
Require user choice before sending a request to a credential manager w3c-fedid/digital-credentials#601, by @marcoscaceres.
-
-
5 pull requests merged.
-
Return the coordinator to idle after the virtual wallet responds or declines w3c-fedid/digital-credentials#606.
-
Editorial: move the coordinator's reset steps into two algorithms w3c-fedid/digital-credentials#604.
-
Replace mediation "MUST NOT throw" prose with [[implicitMediation]] slot w3c-fedid/digital-credentials#511.
-
Add document origin to request context w3c-fedid/digital-credentials#512.
-
Clarify network and protocol tampering threats w3c-fedid/digital-credentials#493.
-
-
1 pull request closed.
-
Skip requests that fail validation instead of throwing w3c-fedid/digital-credentials#554.
-
-
16 pull requests received 53 new comments.
-
Add document origin to request context w3c-fedid/digital-credentials#512 (10 comments by @marcoscaceres, @mohamedamir)
-
fix: return the coordinator to idle when the requesting document stops being fully active w3c-fedid/digital-credentials#603 (6 comments by @marcoscaceres, @mohamedamir)
-
Privacy Considerations: ecosystem note and per-protocol privacy review w3c-fedid/digital-credentials#543 (5 comments by @marcoscaceres, @mohamedamir)
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520 (5 comments by @marcoscaceres, @mohamedamir, @simoneonofri)
-
Add privacy considerations on private browsing mode and clearing site data w3c-fedid/digital-credentials#602 (5 comments by @mohamedamir)
-
Return the coordinator to idle after the virtual wallet responds or declines w3c-fedid/digital-credentials#606 (3 comments by @marcoscaceres, @mohamedamir)
-
Additional Privacy Considerations text w3c-fedid/digital-credentials#598 (3 comments by @marcoscaceres, @mohamedamir)
-
Privacy Considerations: state the user agent's baseline linkability assumption w3c-fedid/digital-credentials#528 (3 comments by @mohamedamir)
-
Editorial: move the coordinator's reset steps into one algorithm w3c-fedid/digital-credentials#604 (2 comments by @marcoscaceres, @mohamedamir)
-
Clarify network and protocol tampering threats w3c-fedid/digital-credentials#493 (2 comments by @marcoscaceres)
-
Apply friction when a request carries no signature to check w3c-fedid/digital-credentials#575 (2 comments by @mohamedamir)
-
Updated "Data Clearing and Persistent State" with private browsing considerations w3c-fedid/digital-credentials#599 (2 comments by @marcoscaceres, @ZAnsaroudi)
-
Reject with the abort reason if the signal aborts during validation w3c-fedid/digital-credentials#608 (1 comment by @marcoscaceres)
-
w3c-fedid/digital-credentials#605 (1 comment by @w3cbot)
-
w3c-fedid/digital-credentials#600 (1 comment by @w3cbot)
-
w3c-fedid/FedCM
-
2 issues opened.
-
Double ccounts on many apps w3c-fedid/FedCM#865, by @tfraney.
-
-
1 issue received 1 new comment.
-
w3c-fedid/FedCM#429 (1 comment by @kz706510-cmd)
-
-
12 pull requests opened.
-
Add optional branding field to IdentityProviderWellKnown w3c-fedid/FedCM#863, by @lang98.
-
Parse and pass the FedCM provider origin for account login status w3c-fedid/FedCM#862, by @JinDX.
-
Read the FedCM mode from the identity request options w3c-fedid/FedCM#861, by @JinDX.
-
Pass the calling global to the FedCM getUserInfo algorithm w3c-fedid/FedCM#860, by @JinDX.
-
Reuse the parsed origins in FedCM auto-reauthentication eligibility w3c-fedid/FedCM#859, by @JinDX.
-
Fix the manifest fingerprinting example w3c-fedid/FedCM#858, by @JinDX.
-
Bind the credential in the FedCM login example w3c-fedid/FedCM#857, by @JinDX.
-
Pass the login dialog context and resolve relative URLs w3c-fedid/FedCM#856, by @JinDX.
-
Set Content-Type on FedCM form requests w3c-fedid/FedCM#855, by @JinDX.
-
Fix the label_hints key in the accounts JSON example w3c-fedid/FedCM#854, by @JinDX.
-
Return after rejecting in attempt to disconnect w3c-fedid/FedCM#853, by @JinDX.
-
Set user-agent-no-cors on no-cors requests w3c-fedid/FedCM#852, by @zcorpan.
-
TR publications
-
3 documents published.
-
Digital Credentials published 3 times as a Working Draft. History of Digital Credentials
-
Past meetings
-
7 meetings.
Participants
-
3 participants joined.
-
Christian Bormann (Common Codes GmbH) joined.
-
Matthew Miller (OneSpan) joined.
-
Mallikarjuna Potta (PayPal) joined.
-
-
6 participants left.
-
David Pham (The Washington Post) left.
-
Phil Smart (W3C Invited Experts) left.
-
Tejas Dhagawkar (Microsoft Corporation) left.
-
Matthew Miller (Cisco) left.
-
Christian Bormann (SPRIND GmbH) left.
-
Kristina Yasuda (SPRIND GmbH) left.
-
-
2 organizations joined.
-
Common Codes GmbH joined.
-
PayPal joined.
-
-
1 organization left.
-
SPRIND GmbH left.
-
GitHub
w3c-fedid/digital-credentials
-
5 issues opened.
-
The DC API is unusable on Android devices without Google Play services w3c-fedid/digital-credentials#597, by @dzuluaga.
-
The user-activation requirement forces a redundant tap in cross-origin iframe and cross-site redirect flows w3c-fedid/digital-credentials#596, by @mallikarjunap.
-
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.
-
-
17 issues received 31 new comments.
-
Conditional invocation for Digital Credential presentation requests w3c-fedid/digital-credentials#587 (7 comments by @mallikarjunap, @marcoscaceres, @RByers, @timcappalli, @wseltzer)
-
Annex C being optional w3c-fedid/digital-credentials#578 (6 comments by @c2bo, @marcoscaceres, @TallTed)
-
Wallet Selection Binding during Issuance w3c-fedid/digital-credentials#382 (3 comments by @c2bo, @leecam, @wseltzer)
-
Document the role of architectural layering in the Digital Credentials API w3c-fedid/digital-credentials#589 (2 comments by @marcoscaceres, @wseltzer)
-
The user-activation requirement forces a redundant tap in cross-origin iframe and cross-site redirect flows w3c-fedid/digital-credentials#596 (1 comment by @RByers)
-
Issuer identity in selective disclosure cases w3c-fedid/digital-credentials#139 (1 comment by @RByers)
-
The DC API is unusable on Android devices without Google Play services w3c-fedid/digital-credentials#597 (1 comment by @timcappalli)
-
Most users will experience a no-matching-credential dead-end w3c-fedid/digital-credentials#104 (1 comment by @dzuluaga)
-
Ensure that credential issuers do not discriminate based on the user’s device or OS w3c-fedid/digital-credentials#349 (1 comment by @dzuluaga)
-
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)
-
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)
-
-
6 pull requests opened.
-
Updated "Data Clearing and Persistent State" with private browsing considerations w3c-fedid/digital-credentials#599, by @tjwhalen.
-
Additional Privacy Considerations text w3c-fedid/digital-credentials#598, by @tjwhalen.
-
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.
-
-
4 pull requests merged.
-
Add security considerations on forged credential chooser requests w3c-fedid/digital-credentials#506.
-
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.
-
-
9 pull requests received 45 new comments.
-
Specify protocol validation + enforce encryption w3c-fedid/digital-credentials#520 (18 comments by @c2bo, @marcoscaceres, @martijnharing, @timcappalli)
-
Add verifier hardening guidance for script injection w3c-fedid/digital-credentials#539 (17 comments by @marcoscaceres, @mikewest)
-
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)
-
Update API to return an array of DigitalCredential instances w3c-fedid/digital-credentials#531 (1 comment by @RByers)
-
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
-
2 issues opened.
-
Reuse the JSON Web Token Claims registry for the accounts endpoint w3c-fedid/FedCM#851, by @ThisIsMissEm.
-
Duplication between well-known web-identity and config.json on IdP w3c-fedid/FedCM#850, by @ThisIsMissEm.
-
-
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.
-
-
10 issues received 13 new comments.
-
Reuse the JSON Web Token Claims registry for the accounts endpoint w3c-fedid/FedCM#851 (3 comments by @ThisIsMissEm)
-
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)
-
-
3 pull requests opened.
-
Add optional icons field to IdentityProviderClientMetadata w3c-fedid/FedCM#849, by @lang98.
-
Added Privacy Policy, Terms of Service, Account Manager Url fields to IDP Config file w3c-fedid/FedCM#847, by @abhishekmadan30.
-
-
1 pull request merged.
-
1 pull request closed.
-
1 pull request received 2 new comments.
-
Strictly Editorial Refactoring to make merging/extending the Registration, Delegation and Accounts Push spec easier w3c-fedid/FedCM#848 (2 comments by @samuelgoto)
-
w3c-fedid/meetings
-
1 pull request opened.
-
Update FedCM agenda timings and add new session for unifying mediated… w3c-fedid/meetings#8, by @samuelgoto.
-
-
3 pull requests merged.
-
Update notes on requestOrigin attribute discussion w3c-fedid/meetings#7.
-
Fix a transcription error w3c-fedid/meetings#6.
-
Update FedCM agenda timings and add new session for unifying mediated… w3c-fedid/meetings#8.
-
-
3 pull requests received 3 new comments.
-
Update FedCM agenda timings and add new session for unifying mediated… w3c-fedid/meetings#8 (1 comment by @wseltzer)
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.