-
Concerns
- JSONPath: security issues
- 2.1 breaking change
Structure of PE spec
- base: simple stuff
- features: advanced, under-defined
Structurally better to have jsonpointer at the base l…
-
This means you can remove the credentialExchangeRecord and still have the credential data.
In addition, we should start looking at promoting the usage of the credential records itself more over the…
-
After reading the document, it's not clear what is the use of this nonce and when and why you would need to request a nonce from the nonce endpoint.
The abstract references [RFC6749](https://www.rf…
-
> As I stated in the WG Call, I believe that `credential_configuration_id` is the better choice. In general, I have trouble understanding how OpenID4VCI works well without metadata, as the Wallet need…
-
We will need to update our error to use "invalid_proof" instead and add backwards compatibility code into our client software.
-
In 23220-3 the goal is to focus on building blocks however there will be a toy-like protocol defined in an informative annex which uses the protocol. This is mainly for interoperability testing. The p…
-
As was raised recently during the DCP WG face to face call.
If a wallet is making use of cryptographic keys that require some form of user authentication in order to perform a cryptographic operati…
-
WDYT about?
`wallet_issuer` -> `wallet_provider`
it seems more closer to the current language
_Originally posted by @peppelinux in https://github.com/openid/OpenID4VCI/pull/98#d…
-
My colleagues and I never really understood the parameters wallet_issuer and user_hint and this PR doesn't solve that either. I think the specification is missing text on this, but unsure if this shou…
-
There were different interpretations during the LSP interop event whether the `iss` element in key proof (both jwt and cwt) is conditionally required or generally optional?
In Section [7.2.1.1. ](h…