OAuth2 & OpenID Connect Debugger — VC Issuance (choose a use case)

There is more than one way for a credential to end up in a wallet, and OID4VCI describes them in its Use Cases appendix. They differ in who starts, how the wallet learns what is on offer, and which grant does the authorizing — so pick one and the rest of the workflow follows it. You can come back and change it at any time; nothing you have already configured is lost.

VC Tools

Tools that are useful at any point in these workflows, and belong to none of their steps.

DID Tools Resolve a DID to its document, read the keys it publishes, check that one of them really signed the credential this browser is holding, and check that the DID and an origin are the same entity.	Resolve a Decentralized Identifier (`did:jwk`, `did:key`, `did:web`) to its document, verify that a key it publishes signed the credential in this browser, and verify a domain linkage (DIF Well Known DID Configuration). Opens in this tab; the workflow's state is untouched.
Certificate Authority & X.509 Tools Build a Root, Intermediate and Issuing CA, issue certificates with any X.509v3 extension, and test a real TLS or mutual-TLS handshake with what you issued.	Build a certificate authority — Root, Intermediate and Issuing — and issue TLS server, TLS client, code-signing and S/MIME certificates with full X.509v3 extension control. Useful when the issuer or verifier is behind TLS you control. Opens in this tab; the workflow's state is untouched.

VC Issuance — How do you want to start?← Return to home