-
Notifications
You must be signed in to change notification settings - Fork 9
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[spec] Add blurb about wallets being a second user agent
spec
#190
opened Nov 18, 2024 by
timcappalli
Top level request object structure should be fully defined by protocol identifier
oidf:dcp
Discussion with OIDF DCP WG
registry
registry related
spec
#185
opened Oct 23, 2024 by
timcappalli
Don't require CM "mediation" to be specified explicitly (always 'required' for DC).
pending closure
#177
opened Oct 7, 2024 by
samuelgoto
What is the defined trust boundary between the user, wallet, and browser?
#166
opened Sep 9, 2024 by
kdenhartog
Describe trust signals in protocol registry
registry
registry related
#136
opened Jun 26, 2024 by
npdoty
Consider requiring mitigation of script injection attacks.
future
#133
opened Jun 24, 2024 by
mikewest
[spec] DigitalCredentialRequestOptions and DigitalCredential objects must be JSON serializable
cgr1-blocker
Community Group Report 1 Blocker
spec
[spec] add statement about responses with PII MUST be encrypted
registry
registry related
spec
#124
opened Jun 11, 2024 by
timcappalli
Access to an Open Global Web Reduced
discussion
mozilla
#123
opened Jun 10, 2024 by
bvandersloot-mozilla
Should requests be assumed to be linkable by the browser?
#122
opened Jun 10, 2024 by
bvandersloot-mozilla
Should we have a common and interoperable definition of request types and their privacy properties?
discussion
#117
opened May 20, 2024 by
samuelgoto
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.