DIIPv5 Testsuite - please test the testsuite

[k00ij]

Good news. There is an initial DIIPv5 test suite (thanks a lot Nikos!).
It's a copy of the DIIPv4 testsuite but updated to reflect the changes (move to OID4VCI and VP v1.0).
All wallet providers that already have access to the Open ITB should see this new DIIPv5 testsuite.

We realise that this testsuite may not yet be bullet proof. So our question to all of you: can you run these new DIIPv5 test cases and provide us your feedback overhere (or post an Issue)?

Thanks a lot and lets try to asap get a solid DIIPv5 testsuite.

[nanderstabel]

Thank you, Nikos, for adding the DIIPv5 test suite!

Everything seems to work just fine in UniMe (unrealeased version) so far except for Test case 000008: VP DIIP v4 did:web direct_post get and sdjwt and
Test case 000010: VCI pre-authorization code flow - PIN - sdjwt With Revocation because the did:web DID Document that is used in these test cases seem to have an invalid controller and verification method id (in the authentication array):

{
  "@context": "https://www.w3.org/ns/did/v1",
  "id": "did:web:itb.ilabs.ai:diipv5",
  "verificationMethod": [
    {
      "id": "did:web:itb.ilabs.ai:diipv5#keys-1",
      "type": "JsonWebKey2020",
      "controller": "itb.ilabs.ai:diipv5",                                       // <-- this should be "did:web:itb.ilabs.ai:diipv5"
      "publicKeyJwk": {
        "kty": "EC",
        "x": "ijVgOGHvwHSeV1Z2iLF9pQLQAw7KcHF3VIjThhvVtBQ",
        "y": "SfFShWAUGEnNx24V2b5G1jrhJNHmMwtgROBOi9OKJLc",
        "crv": "P-256"
      }
    }
  ],
  "authentication": [
    "itb.ilabs.ai:diipv5#keys-1"                                                 // <-- this should be "did:web:itb.ilabs.ai:diipv5#keys-1" or just "#keys-1"
  ],
  "service": [
    {
      "id": "did:web:itb.ilabs.ai:diipv5#jwks",
      "type": "JsonWebKey2020",
      "serviceEndpoint": "https://itb.ilabs.ai/diipv5/.well-known/jwks.json"
    }
  ]
}

[endimion]

hey @nanderstabel good catch it seems if forgot to update this! Will deploy a fix in after a few morning meetings

[nanderstabel]

Seems like for Test case 000002: VCI pre-authorization code flow - PIN - sdjwt the issued credential's typ header value is set to vc+sd-jwt, but it should be dc+sd-jwt.

Same goes for Test case 000010: VCI pre-authorization code flow - PIN - sdjwt With Revocation and I assume the other test cases that include sdjwt as well.

[endimion]

think my mistake came from: https://www.w3.org/TR/vc-jose-cose/#vc-json-sd-jwt deploy a fix with the above many thanks!