Skip to content

Issues: WICG/digital-credentials

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

52 Open 76 Closed
52 Open 76 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

enumerated values for purpose, sharing and retention in API method
#209 opened Mar 11, 2025 by npdoty
require in-context in-content explanation and an element for user-initiated presentation
#208 opened Mar 11, 2025 by npdoty
1
Issuance: multiple requests
#207 opened Mar 11, 2025 by timcappalli
WICG Digital Credentials group consensus to move work FPWD Blockers Should be addressed before FPWD
#206 opened Mar 11, 2025 by timcappalli
Intent to Migrate: Digital Credentials FPWD Blockers Should be addressed before FPWD
#205 opened Mar 1, 2025 by marcoscaceres
@simoneonofri
8
[spec] Requests' size should be checked before transient activation spec
#202 opened Jan 26, 2025 by marcoscaceres
multi-wallet requests
#201 opened Jan 22, 2025 by Sakurann
2
Add getClientCapabilities method for feature detection spec
#200 opened Jan 16, 2025 by timcappalli
4
The digital credential definition should include "verifiable" aspect
#198 opened Jan 8, 2025 by marcoscaceres
1
What are the protocol identifier naming rules? registry registry related spec
#191 opened Dec 4, 2024 by timcappalli
15
Top level request object structure should be fully defined by protocol identifier FPWD Blockers Should be addressed before FPWD oidf:dcp Discussion with OIDF DCP WG registry registry related spec
#185 opened Oct 23, 2024 by timcappalli
@timcappalli
6
[spec] write security considerations spec
#184 opened Oct 21, 2024 by npdoty Community Group Report 1
@marcoscaceres
3
[spec] write privacy considerations spec
#183 opened Oct 21, 2024 by npdoty Community Group Report 1
2
Don't require CM "mediation" to be specified explicitly (always 'required' for DC). spec:credman
#177 opened Oct 7, 2024 by samuelgoto
@samuelgoto
5
Add a way to check what protocols are supported
#168 opened Sep 12, 2024 by marcoscaceres
@marcoscaceres
18
Support for issuance FPWD Blockers Should be addressed before FPWD issuance
#167 opened Sep 9, 2024 by samuelgoto
1
@samuelgoto
18
What is the defined trust boundary between the user, wallet, and browser?
#166 opened Sep 9, 2024 by kdenhartog
7
Handling various origin types spec
#160 opened Aug 20, 2024 by marcoscaceres
@marcoscaceres
4
[spec] Handling ongoing operations / subsequent call to get() spec
#159 opened Aug 18, 2024 by marcoscaceres
@marcoscaceres
1
Issuer identity in selective disclosure cases
#139 opened Jun 26, 2024 by martinthomson
8
Describe trust signals in protocol registry registry registry related
#136 opened Jun 26, 2024 by npdoty
6
Consider requiring a strong signal of user intent. future
#134 opened Jun 24, 2024 by mikewest
6
Consider requiring mitigation of script injection attacks. future
#133 opened Jun 24, 2024 by mikewest
3
Define WebDriver integration
#131 opened Jun 22, 2024 by RByers
2
Define error handling spec
#130 opened Jun 21, 2024 by RByers
1
@RByers
4
ProTip! Type g i on any issue or pull request to go back to the issue listing page.