-
The Nuts community builds a DID, OpenID4VCI and OpenID4VP implementation in the form of the Nuts node: https://github.com/nuts-foundation/nuts-node. It's not a mobile user wallet in the typical "walle…
-
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…
-
Is there anything being planned for supporting the issuance of credentials to wallets that don't have a pre-registered OAuth Client on the issuer's AS?
Q1: I presume that in open and low assurance …
-
There is an implicit understanding that parameters such as `nonce`, `client_id` and `client_id_scheme` are used in VPs but we don't have explicit language how this is done for specific format identifi…
awoie updated
1 month ago
-
I was playing around with the example and I noticed two things regarding how some of the SIOPv2 specifications are implemented.
Firstly, I noticed that when Authorization Response is returned to t…
-
Have the Nuts node as verifier request a VP from a mobile wallet (Sphereon Wallet for now) to have a care professional provision their identity.
- [ ] Implement authz request object passing through…
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1925
### Original Reporter: KristinaYasuda
When PAR is used in OID4VP, does client\_assertion\_type parameter repl…
-
Referring to Section 4 "The Four-Party Model":
1. the relationship between Holder, Wallet Provider, Wallet Solution, End-User and End-User's Wallet should be clarified. They are all mentioned in th…
-
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.
…
-
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…