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

[Gail Hodges]

Edward, Confirmed with thanks! Can you please confirm the name and title of the person to whom we should attribute your quote in our comms?

Joseph, Thomas- can you confirm you have received the information from Juba provided from Lissi via email (probably to certification at oidf.org email) and that you have closed out that feedback or it is confirmed as logged and underway?

Gail

From: Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols-bounces at lists.openid.net> on behalf of Edward Curran via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols at lists.openid.net>
Date: Wednesday, April 29, 2026 at 12:50 AM
To: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net>
Cc: Edward Curran <edward.curran at lissi.id>, Adrian Doerk <adrian.doerk at lissi.id>
Subject: Re: [Openid-dcp] Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)

Hi,

I'm Edward From Lissi.

1. oid4vci-1_0-issuer-haip-test-plan (SD-JWT), oid4vci-1_0-issuer-test-plan (SD-JWT, pre-auth), oid4vp-1final-verifier-haip-test-plan(SD-JWT)
2. I have actively submitted bug reports/gaps to the GitLab repository. My colleague (Juba) has shared feedback about the conformance suite's usability via email. For passing results, I can share for oid4vp soon. For oid4vci, we are still adding support for the newly added fapi tests. We have integrated the conformance suite into our release pipeline and run an automated test against the demo system once a day.
3. Use my contact as the lead contact: Edward Curran (edward.curran at lissi.id<mailto:edward.curran at lissi.id>)
4. Yes we would like to be included by name in launch communications. Initial quote: "The OpenID4VC test suite greatly facilitates the practical implementation of use cases with digital identity wallets and ensures global interoperability."
5. already signed

Kind regards,
Edward

On Tue, 28 Apr 2026 at 22:16, Gail Hodges via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols at lists.openid.net<mailto:openid-specs-digital-credentials-protocols at lists.openid.net>> wrote:
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:  https://docs.google.com/spreadsheets/d/1m2BetPvCWw5wFkoAyaQUWnB6NHHKBxiLXu7JiFrtrpg/edit?gid=0#gid=0:

  1.
What tests you ran/are running
  2.
That all feedback you have is submitted to certification at oidf.org<mailto: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

--
Openid-specs-digital-credentials-protocols mailing list
Openid-specs-digital-credentials-protocols at lists.openid.net<mailto:Openid-specs-digital-credentials-protocols at lists.openid.net>
https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols

________________________________

Lissi GmbH

Eschersheimer Landstraße 6,

60322 Frankfurt am Main - GERMANY

District court: Frankfurt am Main, HRB 132758

VAT Tax-ID: DE364109644

Managing Directors: Helge Michael, Sebastian Bickerle, Adrian Doerk


The content of this e-mail is intended exclusively for the designated addressee. If you are not the intended addressee of this e-mail or their representative, please note that any form of publication, reproduction or transmission of the contents of this e-mail is prohibited.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260527/8ff97f00/attachment-0001.htm>