What to trust to test with eudi.tools
eudi.tools signs with two certificates, for two different jobs, and each belongs in a different list. If you run an Authorization Server, an issuer or a verifier and want it to accept eudi.tools, install the one for your side. Check the fingerprint against what you install. Both are test infrastructure: trust them on test systems only.
Wallet provider
Signs the Wallet Attestation (WIA) and the key attestation (KA) this wallet sends to an Authorization Server, and the status list those attestations point into. Put it in your Authorization Server's Wallet Provider list. The wallet authenticates as client https://eudi.tools.
This certificate vouches for everyone using eudi.tools, not for one browser: the wallet provider attests any key presented to it. Add it to a test server's trust list and nothing you care about.
- subject
- C=NL, O=eudi.tools, CN=eudi.tools wallet provider root (synthetic)
- issued by
- itself (self-signed)
- valid
- 18 November 2026 to 15 November 2036
- SHA-256
- C6:F1:99:63:9A:31:59:99:0C:20:21:F6:8B:1D:E1:03:8C:7F:16:3C:37:74:6B:38:1F:80:AD:77:F7:77:42:BD
Issuer test root
The root of the chain on every test credential eudi.tools issues, such as the one from “Get a test PID”. A credential carries only the leaf below, never the root, so a verifier gets the root from here. Put it in your verifier's PID Provider list.
Its signing key is published in the eudi.tools repository, so anyone can sign credentials that chain to it. Trusting it means choosing to accept synthetic credentials.
- subject
- C=NL, O=eudi.tools, CN=eudi.tools test root
- issued by
- itself (self-signed)
- valid
- 30 August 2026 to 27 August 2036
- SHA-256
- 15:C1:21:65:9E:10:D2:34:C0:34:F3:2B:3E:8E:F0:24:48:1A:EE:B0:EE:87:CA:C5:D2:B6:68:47:27:5B:88:D4
the leaf it signs, which credentials carry in x5c
- subject
- C=NL, O=eudi.tools, CN=dev.eudi.tools
- issued by
- C=NL, O=eudi.tools, CN=eudi.tools test root
- valid
- 30 August 2026 to 27 August 2036
- SHA-256
- 9F:2A:C1:B8:B5:12:3B:11:13:98:52:92:D1:BC:84:4B:98:E6:C3:EF:75:6F:8A:6F:4E:B2:F1:35:A4:39:3B:90
Why not one list for both
They are unrelated keys, and neither works in the other's place. The wallet provider certificate in a PID Provider list, or the issuer root in a Wallet Provider list, fails as “chain does not lead to a trusted root”. That message is about the chain, which is intact, rather than about the certificate, which is the wrong one. If you see it, check which list you used first.
For code: /api/wallet-attestation and /api/issuer/trust-anchor return the same certificates as JSON.