[Openid-dcp] Last Call! Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)

Niels Klomp nklomp at sphereon.com
Wed May 27 22:31:09 UTC 2026 

Hi Gail,

I don't see Sphereon listed, whilst we do actually pass issuer and verifier tests for OID4VC/HAIP 1.0.

Copied the text from a few weeks ago


First of all, congrats on the great work on the certification tests! Since we last used it almost a year ago, a lot of valuable tests have been added.


  1.
We ran the following conformance tests for OID4VCI (both wallet and issuer initiated), OID4VP and AS with both sd-jwt and mdocs using our new Open-Source multiplatform Identity Development Kit<https://docs.sphereon.com/idk/guides/getting-started/>. All 6 testplans ran successfully and with minor issues. Only some nits have been reported. Our wallets (mobile and web) will likely follow in 3-4 weeks, given we are still on our old SDK there. We might test them headless, like the suite does itself as well.
  2.
We have sent multiple feedback items, happy to create bug reports as well. I think the biggest improvement item would be the amount of overlap if you run testplans for both credential formats and both wallet and issuer initiated flows. Especially the number of tests for VCI is enormous, which is a good thing, but you have something like 80% or 90% overlap running them 4 times.
  3.
Lead contact: Niels Klomp, CTO Sphereon, nklomp at sphereon.com
  4.
Yes, Sphereon wants to be named in comms. Quote: "Sphereon has been developing open-source libraries for the OpenID specification for credential issuance and verification since early drafts. We know from experience that interoperability is hard and although conformance is not to be confused with interoperability, it is the absolute prerequisite for any self-respecting solution!"
  5.
Signed for all WGs


Kind regards,

Met vriendelijke groet,


Niels Klomp

CTO



[cid:fc5bee56-b0e8-41aa-9d03-65b4a25de3fd]


J.M. Keynesplein 10
1066 EP Amsterdam

+31 (0)852 736513

Op woensdagmiddag niet aanwezig


[cid:c379d842-4a88-4518-9849-ef2fc8f17da0]<https://outlook.office.com/bookwithme/user/ef3b1d5aa847400582b6e64de43cd9d9@sphereon.com?anonymous&ep=signature>
Maak een afspraak voor een gesprek met mij<https://outlook.office.com/bookwithme/user/ef3b1d5aa847400582b6e64de43cd9d9@sphereon.com?anonymous&ep=signature>
________________________________
Van: Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols-bounces at lists.openid.net> namens Gail Hodges via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols at lists.openid.net>
Verzonden: woensdag 27 mei 2026 22:26
Aan: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net>
CC: Gail Hodges <gail at oidf.org>; Joseph Heenan <joseph.heenan at oidf.org>; Serj Hallam <serj.hallam at oidf.org>
Onderwerp: [Openid-dcp] Last Call! Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)

Hello DCP WG Implementers

This is the Final Call to "test the tests" for OpenID4VP 1.0, OpenID4VCI 1.0, and HAIP 1.0, feedback due by June 2nd.

We have feedback from 5 implementers (Bundesdruckerei, Lissi, Meeco, Hopae, UIDAI/Aadhaar). Another 6 implementers confirmed that they plan to provide feedback.  We are trending towards having the minimum feedback required for the WG to confirm that the test suite meets requirements, and it can be published for self-certification.


If you want to take part, we need to know:

  1.  What tests you ran
        *   OpenID4VP 1.0 + HAIP 1.0 for SD-JWT and/or  mdoc, as wallet
        *   OpenID4VP 1.0 + HAIP 1.0 for SD-JWT and/or  mdoc, as verifier
        *   OpenID4VPVCI 1.0 + HAIP 1.0for SD-JWT and/or  mdoc, as issuer
        *   OpenID4VPVCI 1.0 + HAIP 1.0for SD-JWT and or mdoc,  as wallet
  2.
Test logs for the tests you ran
  3.  Any feedback on tests themselves, issues bugs, or let us know if it worked as expected
  4.  Entity name, permission to use entity name or not
  5.  Entity logo, permission to use entity logo or not
  6.  Quote if you want to be included in comms, and if so the name and title to attribute quote to
  7.  Confirmation that a signed contribution agreement is in place (to cover feedback)
  8.  Confirmation if membership is in place or not (not required to be a member, we are tracking however)

I can update the tracker for you:

https://docs.google.com/spreadsheets/d/1Zfp41ah1u2JCdnjv6NvcTF7k4TJnlBjBkwr4Fp--stg/edit?gid=0#gid=0


Tests are located in usual place:

  *
OpenID for Verifiable Presentations<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/
  *   OpenID for Verifiable Credential Issuance<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/

It is not required for your configuration to pass all tests for your feedback to be welcome. There is also value in knowing that tests that do not pass, fail to pass for expected reasons.

Only after the  WG approves the test suite is ready, and OIDF “launches,” the test suite will they be made available for self-certification. At this stage, for modest fees, any implementer can submit their test results for OIDF review and publication of passing results on OIDF website. At this point no fees apply we are solely proving out the open source test suite.  Open source projects do not have to pay fees to submit their results for self-certification.



Gail





From: Gail Hodges <gail at oidf.org<mailto:gail at oidf.org>>

Date: Tuesday, April 28, 2026 at 1:15 PM

To: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net<mailto:openid-specs-digital-credentials-protocols at lists.openid.net>>

Cc: Joseph Heenan <joseph.heenan at oidf.org<mailto:joseph.heenan at oidf.org>>, Thomas Darimont <thomas.darimont at oidf.org<mailto:thomas.darimont at oidf.org>>

Subject: Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)


Hello all


Hello leading implementers of OpenID4VP 1.0, OpenID4VCI 1.0 and HAIP 1.0! Many thanks to all of you who have been testing the tests in interop this past year.


We need your help.


We need at least 3 issuers,  3 wallets and 3 verifiers to “tests the tests” for the test suite to make sure they are fully debugged, so OIDF can launch the open source test suite. Tests are located in usual place:

  *   OpenID for Verifiable Presentations<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/
  *   OpenID for Verifiable Credential Issuance<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/> 1.0 + HAIP 1.0https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/

Please use the ‘demo’ system to test as per the above instructions; that has the latest changes/fixes applied.

From: Gail Hodges <gail at oidf.org>
Date: Tuesday, April 28, 2026 at 8:15 PM
To: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net>
Cc: Joseph Heenan <joseph.heenan at oidf.org>, Thomas Darimont <thomas.darimont at oidf.org>
Subject: Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)

Hello all

Hello leading implementers of OpenID4VP 1.0, OpenID4VCI 1.0 and HAIP 1.0! Many thanks to all of you who have been testing the tests in interop this past year.

We need your help.

We need at least 3 issuers,  3 wallets and 3 verifiers to “tests the tests” for the test suite to make sure they are fully debugged, so OIDF can launch the open source test suite. Tests are located in usual place:

  *
OpenID for Verifiable Presentations<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/
  *
OpenID for Verifiable Credential Issuance<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/

Please use the ‘demo’ system to test as per the above instructions; that has the latest changes/fixes applied.
We are using this template to track your feedback, and you appetite to be included in the OIDF comms launching the conformance test suite:

  1.
What tests you ran/are running
  2.
That all feedback you have is submitted to certification at oidf.org (including passing results, bugs or gaps)
  3.
Your lead person contact person and their contact information (if different to what we have shown for you )
  4.
If you want your entity to be named in comms, and a quote if you want to give one.
  5.
If you do not have a DCP WG contribution agreement signed, please complete it to IPR protect your feedback   https://openid.net/intellectual-property naming  DCP WG or better yet  "ALL WGs."

The Certification team will triage feedback, with WG feedback where needed.
Once the test suite is live, the following conformance capabilities will be enabled:

  *
Self-certification will launch
     *
Entities will have the option but not the obligation to self-certify for modest fees, discounts for members.
     *
Tests available
        *
OpenID4VP 1.0 + HAIP 1.0 for SD-JWT and mdoc (Note: not generic VP )
        *
OpenID4VPVCI 1.0 + HAIP 1.0for SD-JWT and mdoc  (Note: not generic VCI)
  *
OIDF will be launching a new Independent Conformance Service, where third parties may be accredited to operate the conformance suite on behalf of OIDF to operate conformance.
     *
Program to launch in Q2
     *
First 6 MOU signatories were announced in March & April.
  *
OIDF will continue to collaborate with and brief leading ecosystems like EC, California, India, Brazil, World Bank (for their clients), as well as peer standards bodies (e.g. CSC, FIDO, W3C etc)

Thanks in advance!

Joseph, Thomas, Gail

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260527/d621d6ca/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-xhwjvhkh.png
Type: image/png
Size: 13254 bytes
Desc: Outlook-xhwjvhkh.png
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260527/d621d6ca/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-4p04q0yh.png
Type: image/png
Size: 528 bytes
Desc: Outlook-4p04q0yh.png
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260527/d621d6ca/attachment-0003.png>

More information about the Openid-specs-digital-credentials-protocols mailing list