-
Document what a vendor needs to do to start using (receiving, issuing) VCs over OpenID4VCI. Should be as little as possible.
A vendor currently needs to register a wallet metadata URL on each of it…
-
I continue the discussion started in openid/OpenID4VCI#39
> OAuth 2.0 doesn't require AT in JWT format, then the flow must be designed as the AT was opaque. Thus, the (un)security of the AT as a be…
-
# 1.1.0
The TrustBloc Wallet SDK v1.1 supports JSON-LD Verifiable Credential (VC) format, OpenID4VCI Authorization Code Issuance protocol, and minor bug fixes.
## What's New
- SDK
- OpenID4VCI…
-
The regular OpenID4VP, for acquiring an access token given a VP from a wallet, doesn't lend itself for server to server communication. Reasons:
- It starts with the verifier (resource owner) instru…
-
It doesn't have one because it never needed one: all VCs were on the DAG meaning it could be restored from the DAG. But when receiving VCs over OpenID4VCI, they're not backed up (since they're not on …
-
Hi,
I'm playing with the wallet, and for our use case, we would need to pass to the wallet issuance/presentation URLs from other application. Looking at the code, it seems that the URL is passed to…
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1401
### Original Reporter: tlodderstedt
The current cross device flow works fine, however it forces the RP to mak…
-
Regarding the proof in a credential request defined in OID4VCI. The "[Proof Types](https://openid.bitbucket.io/connect/openid-4-verifiable-credential-issuance-1_0.html#name-proof-types)" section in th…
-
Accept credential offers and store them in a persistent store so they can be retried.
Probably needs fields like:
* offered_at
* state (offered, retrieved)
* grant_type (for now only pre-auth)
* gra…
-
See last comment for solution: move to /n2n
---
There currently is no trust store configured, so it falls back to the OS certbundle.
We should decide which certificates parties should use to …