@@ -334,11 +334,12 @@ allure serve allure-results
334
334
335
335
## Implementation
336
336
337
- ### VC-API
338
- To add your implementation to this test suite You will need to add 3 endpoints to your implementation manifest.
339
- - A credentials issuer endpoint (` / credentials/ issue` ) in the ` issuers` property.
340
- - A credentials verifier endpoint (` / credentials/ verify` ) in the ` verifiers` property.
341
- - A presentations verifier endpoint (` presentations/ verify` ) in the ` vpVerifiers` property.
337
+ To add your implementation to this test suite, add a test manifest describing
338
+ your implementation to the
339
+ [` w3c/ vc- test- suite- implementations` ](https://github.com/w3c/vc-test-suite-implementations)
340
+ repo by following the
341
+ [Adding a new implementation](https://github.com/w3c/vc-test-suite-implementations/tree/main?tab=readme-ov-file#adding-a-new-implementation)
342
+ instructions.
342
343
343
344
All endpoints will need the tag ` vc2.0 ` . A simplified manifest will roughly
344
345
look like the following:
@@ -365,16 +366,13 @@ look like the following:
365
366
}
366
367
` ` `
367
368
368
- This example above is for a set of unauthenticated endpoints. You may add zcap
369
- or oauth2 authentication to your endpoints.
369
+ This example above is for a set of unauthenticated endpoints. You may add
370
+ [ZCAP](https://w3c-ccg.github.io/zcap-spec/)
371
+ or OAuth2 authentication to your endpoints.
370
372
371
- See the [vc-test-suite-implementations README here](https://github.com/w3c/vc-test-suite-implementations).
372
-
373
- To run the tests, some implementations require client secrets that can be passed
374
- as env variables to the test script. To see which ones require client secrets,
375
- you can check the
376
- [vc-test-suite-implementations](https://github.com/w3c/vc-test-suite-implementations)
377
- library.
373
+ See the
374
+ [Adding a new implementation](https://github.com/w3c/vc-test-suite-implementations/tree/main?tab=readme-ov-file#adding-a-new-implementation)
375
+ for more information.
378
376
379
377
### Enveloping Proof
380
378
Implementers who rely on an enveloping proof securing mechanism can add the ` EnvelopingProof` tag to their implementation registration.
0 commit comments