-
The holder’s privacy, particularly the aspect of unlinkability, represents a significant advancement in the wallet concept compared to existing credential sharing and authorization frameworks. To enha…
-
There are multiple ways how credential PII and key material is stored and also multiple ways to use this for presentment of the credential. Right now we only support a single method which is storing a…
-
In relation to the trust infrastructure needed by QEAA/EAA providers and by Relying Parties, DC4EU is currently focusing on OID Federation and dPKI-based Trust Frameworks to showcase scalable* and fea…
-
`cryptographic_binding_methods_supported` feels like it's probably a bit under defined.
https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html#section-11.2.3 says…
jogu updated
8 months ago
-
The German [Architecture Proposal Version 2](https://gitlab.opencode.de/bmi/eudi-wallet/eidas-2.0-architekturkonzept/-/blob/main/architecture-proposal.md?ref_type=heads) (from 2024-03-21) lists severa…
-
With the anticipated arrival of Post-Quantum Cryptography (PQC) requiring massive amounts of _binary_ data, CBOR will prove to be a better choice than JSON.
See also: https://github.com/eu-digital-…
-
Based on commentary in this issue about the complexity in PeX and it being viewed as too complicated for a presentation request language (I agree):
https://bitbucket.org/openid/connect/issues/1917/…
-
Is this effort to also include management APIs, i.e. doctype management? Along the same lines, does this include crypto provider selection and management (SEE, USB Device, etc.)
-
While waiting for a simplified Presentation Definition implementation profile for OpenID4VP, within the OpenID DCP WG, we have decided to use OAuth 2.0 scopes within the EUDI WALLET IT trust framework…
-
Privacy has not started to be taken into account in the ARF 1.4. The minimum would be to include the two following properties as mandatory objectives of the architecture:
1. Full unlinkability
2. Ev…