iamops.dev
Argo on X RSS feed
ENEnglish

Tools

SD-JWT and verifiable credential decoder

Paste an SD-JWT or a presentation with a Key Binding JWT. I split it, decode every disclosure, recompute the digests and show which claims the holder revealed.

Runs in your browser. Nothing you paste leaves your device.

Runs in your browser. Nothing you paste is sent anywhere. Don't paste production private keys.

The page makes no network request while you work. The only exceptions are the buttons that say Fetch, which call the address you type. Keep real private keys out of any web page, including this one.

How to get the input
  1. The quickest known-good input is the example in RFC 9901 section 5, with the issuer key from appendix A.5.RFC 9901
  2. For a real credential, request a test one from the EU Digital Identity reference issuer and hold it in the EUDI reference wallet.EUDI issuer · EUDI wallet (GitHub)
  3. To make your own, the open-source sd-jwt-js library or walt.id identity can issue and present SD-JWT VCs locally.sd-jwt-js · walt.id identity
  4. In a wallet to verifier flow, the presentation is the vp_token the wallet posts to the verifier. Copy it from DevTools > Network.Chrome DevTools: Network

Use a test account and throwaway keys. Do not paste production secrets, session cookies or real users' tokens.

What can I paste here#

The compact SD-JWT string, including the ~ separators and, if present, the Key Binding JWT at the end. Optionally paste the issuer JWK or JWKS to verify the signature. Line breaks are ignored.

SD-JWT and VC decoder

Follows RFC 9901.

Samples are made with throwaway keys and example.test names. They mean nothing outside this page.

How to read the result#

What it does not do#

Questions people ask#

What can I paste here

The compact SD-JWT string, including the ~ separators and, if present, the Key Binding JWT at the end. Optionally paste the issuer JWK or JWKS to verify the signature. Line breaks are ignored.

What is an SD-JWT?

A signed JWT where some claims are replaced by salted hashes. The holder sends the matching disclosures only for the claims it wants to reveal. RFC 9901 defines it, and SD-JWT VC builds credentials on top of it.

Why does a disclosure show as not referenced?

Its digest is not in any _sd array or ... entry of the signed payload. The disclosure was changed after issuance, was copied from another credential, or the hash algorithm in _sd_alg does not match.

Related articles#

The newest posts and labs on the same topic, picked automatically.