-
We discussed in the last CG call how to handle registries, and I think we realized as a group that there are two layers here: the protocol layer (e.g. OpenID4VP) and the request type layer (e.g. Prese…
-
Opaque, protocol-specific request strings don't allow site authors to indicate why and how each field in the request will be used, or to provide the context for a user to make a reasonable decision.
…
-
This is split out from https://github.com/openid/OpenID4VP/issues/219 :
> For item 3 "what if verifier wants to pass multiple trust models, hoping one is supported by the wallet?"
>
> This is im…
-
We need to give further details within the documentation about how to configure custom classes
see: https://github.com/italia/eudi-wallet-it-python/pull/256/files#diff-abaed126a367f4b06dfa49959ae14…
-
ISO/IEC SC17/JTC1 WG10 had an in-person meeting in Korea in late June where a demo of the Digital Credentials API was provided (also including cross-device). WG10 asked OIDF if they can help with the …
-
https://github.com/EWC-consortium/ewc-wallet-conformance-backend/blob/staging/routes/verifierRoutes.js
[5. ](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#section-5)[Authoriz…
-
Given that binding to the origin is an important security feature, it is important to give more context on how the origin is used. This means we need to cover the following items in this PR:
* The …
-
This is regarding the implementation of the [Section 5.1.5 Dynamic Credential Request](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-ID1.html#name-dynamic-credential-request). I…
-
Note: This issue is not about enforcing using JAR (#79) or remove client id scheme = redirect_uri (#269).
Reading the spec, it is not clear to me how to use client id scheme = redirect_uri with Au…
-
The spec says:
> expected_origins: REQUIRED when signed requests defined in [Appendix A.3.2](https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html#signed_request) are u…