Giuseppe De Marco
Giuseppe De Marco
There are cases where the Verifier only needs to check the revocation status of a Digital Credential at the time of presentation, and therefore it should not be allowed to...
In docs/annexes/annex-1/annex-1-definitions.md we read that the Trust Anchor is defined as below ```` The public key of an entity that is trusted by a Wallet Instance and used for validating...
This PR aims to resolve part of the comments shared in the issue https://github.com/openid/OpenID4VCI/issues/313
### Problem and Requirement There are cases where a trust framework or federative model introduces the requirement to approve during onboarding, and consequently to include in the client metadata the...
The current definition of "Holder" in the OpenID4VP specifications states: > Holder: An entity that receives Verifiable Credentials and has control over them to present them to the Verifiers as...
Regarding the section [Signed and/or Encrypted Responses](https://github.com/openid/OpenID4VP/blob/main/openid-4-verifiable-presentations-1_0.md#signed-andor-encrypted-responses-jarm). To provide concrete guidance for implementations, I suggest the following change: `To sign, or sign and encrypt the Authorization Response, implementations MAY use...
 ### Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project. #### Snyk changed the following file(s): - `requirements.txt` ⚠️ Warning ``` pysaml2...
the automated SPID compliance test fails after soem changes in the spid validator cose, this might be linked to this https://github.com/italia/Satosa-Saml2Spid/pull/128/files and any other thast have changed the spid_validator.py code...
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...
As promised during the previous DCP WG call, here I create the issue to introduce the value of having the parameters jwks within the openid4vci metadata, as proposed also in...