Daniel Fett

Results 39 issues of Daniel Fett

In https://github.com/openid/OpenID4VCI/pull/140, we defined some rules especially for signed metadata. In general, we should add sections that normatively define how metadata must be processed and verified. This should in particular...

ready-for-PR

For W3C credentials, the field `value_type` is defined as > String value determining the type of value of the claim. A non-exhaustive list of valid values defined by this specification...

issuer-metadata

The current definition of the VP Token has two problems: (1) The current definition of the `vp_token` parameter is hard to read and the use of JSON is somewhat confusing:...

When `client_id_scheme` is used, there can be multiple client_ids in the same ecosystem that belong to different clients. One of those clients could be malicious, compromised or the client_id scheme...

priority
security

Related to #160, #161, #162 and #157. This is a proposal for a new query language fulfilling the requirements discussed in the issues linked above. I can create a PR...

ready-for-PR
query language

The draft currently contains the following references to the OAuth Security BCP: (1) > Any of the OAuth 2.0 related specifications, such as [[RFC9126](https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html#RFC9126)] and [[RFC9101](https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html#RFC9101)], and Best Current Practice...

security

Current examples in Section 6.1 only show W3C VCs. I think the spec would benefit from an SD-JWT (VC) example.

Many of the examples for HTTP requests/responses are indented by two spaces by default, which is not required, and some indentations are inconsistent. The extra indentations should be removed and...

ready-for-PR
editorial

Fixes #178 Todo: - [ ] Determine which "extensions" we want to specify ("intent_to_retain" etc.) - [ ] Determine which format-specific parameters we need - [ ] Define interaction with...

[This comment](https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/pull/160#issuecomment-2117092649) highlighted a problem that we have not addressed explicitly in OpenID4VP yet: The hierarchy idea behind VCTs doesn't translate well into presentation exchange. PE does string matching, but...