From 4279f52ebdcacadb761cd8a157b461c9c13c86aa Mon Sep 17 00:00:00 2001 From: Stefan Wiedemann Date: Mon, 14 Sep 2026 08:46:01 +0200 Subject: [PATCH 1/2] remove outdated walt-id references --- README.md | 3 +-- api/did-registry.yaml | 1 - config/data/config_test.yaml | 3 --- 3 files changed, 1 insertion(+), 6 deletions(-) diff --git a/README.md b/README.md index 324ce004..e4fcd904 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,6 @@ VCVerifier provides the necessary endpoints(see [API](./api/api.yaml)) to offer * [Database](#database) * [Refresh Token](#refresh-token) * [ConfigServer](#configserver) - * [WaltID SSIKit](#waltid-ssikit) * [Usage](#usage) * [Frontend-Integration](#frontend-integration) * [REST-Example](#rest-example) @@ -52,7 +51,7 @@ The following actions occur in the interaction: 1. the Verifier retrieves the Scope-Information from the Config-Service 4. The user approves the wallet's interaction with the VCVerifier and the VerifiableCredential is presented via the OIDC4VP-flow. 5. VCVerifier verifies the credential: - 1. at WaltID-SSIKit with the configured set of policies + 1. with the configured set of policies 2. (Optional) if a Gaia-X compliant chain is provided 3. that the credential is registered in the configured trusted-participants-registries 4. that the issuer is allowed to issuer the credential with the given claims by one of the configured trusted-issuers-list(s) diff --git a/api/did-registry.yaml b/api/did-registry.yaml index 50dfc527..b37f724f 100644 --- a/api/did-registry.yaml +++ b/api/did-registry.yaml @@ -77,7 +77,6 @@ components: items: type: string example: "https://www.w3.org/ns/did/v1" -# Standard defines list of strings but waltId provides object # assertionMethod: # description: "An assertionMethod property is used to specify a URL that contains information about a verificationMethod used for assertions." # type: array diff --git a/config/data/config_test.yaml b/config/data/config_test.yaml index 2deda040..9540344a 100644 --- a/config/data/config_test.yaml +++ b/config/data/config_test.yaml @@ -27,9 +27,6 @@ verifier: "gx:compliance": ValidFromBeforePolicy: {} -ssiKit: - auditorURL: http://waltid:7003 - m2m: authEnabled: false configRepo: From eeb68a5694b3a78631e1ac23041419870ce916dd Mon Sep 17 00:00:00 2001 From: Stefan Wiedemann Date: Mon, 14 Sep 2026 08:48:10 +0200 Subject: [PATCH 2/2] remove outdated issues --- README.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/README.md b/README.md index e4fcd904..f6a9416f 100644 --- a/README.md +++ b/README.md @@ -690,14 +690,6 @@ The response will contain an object like already shown in [byValue](#byvalue). The API implements enpoints defined in [OIDC4VP](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#name-terminology) and [SIOP-2](https://openid.net/specs/openid-connect-self-issued-v2-1_0.html). The OpenAPI Specification of the implemented endpoints can be found at: [api/api.yaml](api/api.yaml). -### Open issues - -The VCVerifier does currently not support all functionalities defined in the connected standards(e.g. [OIDC4VP](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#name-terminology) and [SIOP-2](https://openid.net/specs/openid-connect-self-issued-v2-1_0.html)). Users should be aware of the following points: - -* the verifier does not offer any endpoint to proof its own identity -* requests to the authentication-response endpoint do accept "presentation_submissions", but do not evaluate them -* even thought the vp_token can contain multiple credentials and all of them will be verified, just the first one will be included in the JWT - ## Testing ### Unit Tests