-
It's currently not possible to check what protocols the browser supports so developers won't know if calling .get() will immediately fail (as it requires user activation).
As such, we should then a…
-
OpenID4VP metadata parameter presentation_definition_supported was introduced to ensure presentation definitions within metadata are secured by a trusted third party, preventing over-asking by verifie…
-
The current draft has introduced at least three brand new metadata parameters about openid4vp implementations.
These was introduced for the first time in the following openid4vp github issue:
http…
-
### Description
Add OpenID4VP standard to the Agent for requesting and verifying credentials. Similarly to OpenID4VCI implementation, the agent must have a method to generating an `auth_request` that…
-
Considering that this project already supports an OIDC frontend and requires the SPID and CIE id backend in OIDC and is going to include the OpenID4VP backend, there are enough motivations to propose …
-
- [ ] `./openid4vp/vp.py:9`: # TODO: what if the credential is not a JWT?
- [ ] `./openid4vp/vp.py:21`: # TODO - automatic detection of the credential
check the entire redirect_endpo…
-
The vp_token definition requires that the OpenID4VCI specification is followed for some of the details of the verifiable presentation content. This has a few issues. :
* It is strange that an issua…
-
Is there a workflow for when the native app/mobile web is requesting verification (e.g., Know Your Customer) and the wallet is on the mobile device? The documented flow uses QR codes and requires mul…
-
I think it is related to a PR 175 and especially a discussion [here](https://github.com/openid/OpenID4VP/pull/175/files#diff-3118c9756a1d7b361bb53af8bd9d65666476a27cfeeced56c47a5dccc38eac55R1836)
Q…
-
## Requirements
Implementers ...
- The trust layer should be handled with a neutral member nbame, including several other trust evaluation mechanisms. See poi 1 below.
- MUST be able to define …