I was directly used the docker image, but not find the idp-config.json docker pull waltid/idpkit docker run -p 8080:8080 -e WALTID_DATA_ROOT=/data -v $PWD:/data waltid/idpkit run docker exec -it 4b /bin/bash root@4b4a9b59736e:/waltid-idpkit# ls bin data lib service-matrix.properties signatory.conf

Hi all,

the walt.id home page states that the SSI kit can be built by just invoking docker. However, this seems to result in an error:

Invoking docker build -t ssikit . results in

=> ERROR [walt-build 2/3] RUN ./gradlew clean build 0.2s

[walt-build 2/3] RUN ./gradlew clean build: #18 0.221 /bin/sh: 1: ./gradlew: not found

executor failed running [/bin/sh -c ./gradlew clean build]: exit code: 127

Regards,

Andreas

I am trying to build on my Mac M1. I am experiencing several problems. When I run the build script I get:

* What went wrong:
Unable to calculate the value of the task ':compileJava' property 'javaCompiler'.
> Unable to download a toolchain that matches these requirements: {languageVersion=16, vendor=any, implementation=vendor-specific}
   > Unable to download the toolchain. This may indicate that the combination (version, architecture, release/early access, ...) for the required JDK is not available.
      > Could not read 'https://api.adoptium.net/v3/binary/latest/16/ga/mac/aarch64/jdk/hotspot/normal/eclipse' because it does not exist.

I installed the arm-specific JDK and removed JDE

Matching Java virtual machines (2):
    19 (arm64) "Oracle Corporation" - "Java SE 19" /Library/Java/JavaVirtualMachines/jdk-19.jdk/Contents/Home
    17.0.4 (arm64) "Amazon.com Inc." - "Amazon Corrected 17" /Users/Library/Java/JavaVirtualMachines/corrected-17.0.4.1/Contents/Home
/Library/Java/JavaVirtualMachines/jdk-19.jdk/Contents/Home

I can't figure out why I keep getting the error. I guess it's due to the arm architecture, but I don't know how to fix it. Any ideas?

Summary

I tried to follow the tutorial for EBSI DID registration at the doc site. However, the essif onboard CLI command returns a VA with the title unexpected issuer found in session token.

Note, that the site for getting bearer tokens (https://app.preprod.ebsi.eu/users-onboarding) is no longer available, only its v2 version (https://app.preprod.ebsi.eu/users-onboarding/v2).

Steps to reproduce

1. Go to https://app.preprod.ebsi.eu/users-onboarding/v2
2. Onboard with Captcha (onboarding with EU Login results in an empty token)
3. Choose Desktop Wallet
4. Copy token
5. Create data/ebsi/bearer-token.txt with copied token as content (eyJhb...)
6. CLI="docker container run --rm -p 7000-7004:7000-7004 -itv $(pwd)/data:/app/data docker.io/waltid/ssikit"
7. ${CLI} key gen -a Secp256k1
8. ${CLI} did create -m ebsi -k <key-id>
9. ${CLI} essif onboard -d <did> /app/data/ebsi/bearer-token.txt

Expected result

Steps 1-9 finish successfully, and a valid VA JSON is created in the data/ebsi/<did>/ directory

Actual result

Step 9 logs indicate success:

walt.id SSI Kit 1.11.0-SNAPSHOT (running on Java 17.0.2+8-86)

ESSIF onboarding for DID <did> running...

ESSIF onboarding for DID <did> was performed successfully.

But the content of the data/ebsi/<did>/verifiable-authorization.json file is:

{"title":"unexpected issuer found in session token","status":401,"type":"about:blank"}

The decoded JWT/bearer token header:

{
  "alg": "ES256K",
  "typ": "JWT",
  "kid": "did:ebsi:zr2rWDHHrUCdZAW7wsSb5nQ#keys-1"
}

The decoded JWT/bearer token payload:

{
  "onboarding": "recaptcha",
  "validatedInfo": {
    "success": true,
    "challenge_ts": "2022-07-05T09:00:15Z",
    "hostname": "app.preprod.ebsi.eu",
    "score": 0.9,
    "action": "login"
  },
  "iss": "did:ebsi:zr2rWDHHrUCdZAW7wsSb5nQ",
  "iat": 1657011617,
  "exp": 1657012517
}

DID registration to the EBSI fails although previous steps (onboarding and auth-api flow) complete successfully with a valid token:

# ./ssikit.sh key gen
...
Key "a7faf423f89447f6ab3d23af62dbbc5e" generated.
#
# ./ssikit.sh did create -m ebsi -k a7faf423f89447f6ab3d23af62dbbc5e
...
DID created: did:ebsi:zoNeMQWP5MrBeANEQaa58pY
...
#
# ./ssikit.sh essif onboard --did did:ebsi:zoNeMQWP5MrBeANEQaa58pY data/bearer-token.txt
...
ESSIF onboarding for DID did:ebsi:zoNeMQWP5MrBeANEQaa58pY was performed successfully.
#
# ./ssikit.sh essif auth-api --did did:ebsi:zoNeMQWP5MrBeANEQaa58pY
...
EBSI Authentication API flow for DID did:ebsi:zoNeMQWP5MrBeANEQaa58pY was performed successfully.
# ./ssikit.sh essif did register --did did:ebsi:zoNeMQWP5MrBeANEQaa58pY
...
Could not register DID (after 6 tries to contact EBSI)!

The above is from a Debian machine where the project has been locally built with ./ssikit.sh build (no containers). Same behaviour when running from outside the container with docker run -itv $(pwd)/data:/app/data waltid/ssikit. Do I miss something?

I have tried to build ssikit both on docker and on my local system but i am facing some issues. On my local system, after installing gradle 7 and JDK 17 when I run this command,

gradle clean build

Some test cases fail, I have also attached the logs of test cases which are failing:

Task :test

id.walt.auditor.AuditorApiTest > testGaiaxCredential FAILED
    java.net.SocketTimeoutException at AuditorApiTest.kt:77
        Caused by: java.net.SocketException at AuditorApiTest.kt:77

id.walt.auditor.AuditorApiTest > testPermanentResidentCardCredential FAILED
    java.net.SocketTimeoutException at AuditorApiTest.kt:77

id.walt.auditor.AuditorApiTest > testVerifiableAttestationCredential FAILED
    java.net.SocketTimeoutException at AuditorApiTest.kt:77
        Caused by: java.net.SocketException at AuditorApiTest.kt:77

id.walt.auditor.AuditorApiTest > testVerifiableAuthorizationCredential FAILED
    java.net.SocketTimeoutException at AuditorApiTest.kt:77

id.walt.auditor.AuditorApiTest > testVerifiableDiploma FAILED
    java.net.SocketTimeoutException at AuditorApiTest.kt:77
        Caused by: java.net.SocketException at AuditorApiTest.kt:77

id.walt.auditor.AuditorApiTest > testVerifiableId FAILED
    java.net.SocketTimeoutException at AuditorApiTest.kt:77
        Caused by: java.net.SocketException at AuditorApiTest.kt:77

id.walt.auditor.AuditorCommandTest > 1. verify vp FAILED
    io.kotest.assertions.AssertionFailedError at AuditorTest.kt:76
OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended

320 tests completed, 7 failed, 17 skipped
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 8m 33s
12 actionable tasks: 11 executed, 1 up-to-date

When i try to build ssikit on docker, some test cases also fail as can be seen from the logs:

#18 569.4 > Task :test
#18 1032.9
#18 1033.0 id.walt.auditor.AuditorApiTest > testGaiaxCredential FAILED
#18 1033.0     java.net.SocketTimeoutException at AuditorApiTest.kt:77
#18 1033.0         Caused by: java.net.SocketException at AuditorApiTest.kt:77
#18 1043.2
#18 1043.2 id.walt.auditor.AuditorApiTest > testPermanentResidentCardCredential FAILED
#18 1043.2     java.net.SocketTimeoutException at AuditorApiTest.kt:77
#18 1043.2         Caused by: java.net.SocketException at AuditorApiTest.kt:77
#18 1053.2
#18 1053.2 id.walt.auditor.AuditorApiTest > testVerifiableAttestationCredential FAILED
#18 1053.2     java.net.SocketTimeoutException at AuditorApiTest.kt:77
#18 1053.2         Caused by: java.net.SocketException at AuditorApiTest.kt:77
#18 1063.3
#18 1063.3 id.walt.auditor.AuditorApiTest > testVerifiableAuthorizationCredential FAILED
#18 1063.3     java.net.SocketTimeoutException at AuditorApiTest.kt:77
#18 1063.3         Caused by: java.net.SocketException at AuditorApiTest.kt:77
#18 1073.4
#18 1073.4 id.walt.auditor.AuditorApiTest > testVerifiableDiploma FAILED
#18 1073.4     java.net.SocketTimeoutException at AuditorApiTest.kt:77
#18 1073.4         Caused by: java.net.SocketException at AuditorApiTest.kt:77
#18 1083.4
#18 1083.4 id.walt.auditor.AuditorApiTest > testVerifiableId FAILED
#18 1083.4     java.net.SocketTimeoutException at AuditorApiTest.kt:77
#18 1083.4         Caused by: java.net.SocketException at AuditorApiTest.kt:77
#18 1343.1
#18 1343.1 id.walt.auditor.AuditorCommandTest > 1. verify vp FAILED
#18 1343.1     io.kotest.assertions.AssertionFailedError at AuditorTest.kt:76
#18 1585.0
#18 1585.0 id.walt.auditor.AuditorCommandTest > 2. verify vc FAILED
#18 1585.0     io.kotest.assertions.AssertionFailedError at AuditorTest.kt:91
#18 1826.8
#18 1826.8 id.walt.auditor.AuditorCommandTest > 3. verify vc jwt FAILED
#18 1826.8     io.kotest.assertions.AssertionFailedError at AuditorTest.kt:107
#18 2068.7
#18 2068.7 id.walt.auditor.AuditorCommandTest > 4. verify vp jwt FAILED
#18 2068.7     io.kotest.assertions.AssertionFailedError at AuditorTest.kt:123
#18 2069.8 OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
#18 2356.6
#18 2356.6 id.walt.rest.EssifApiTest > testTimestampById FAILED
#18 2356.6     io.ktor.client.plugins.HttpRequestTimeoutException at Endpoint.kt:248
#18 2621.2
#18 2621.2 id.walt.services.vc.WaltIdJsonLdCredentialServiceTest > testValidateSchemaTsr FAILED
#18 2621.2     io.kotest.assertions.AssertionFailedError at WaltIdJsonLdCredentialServiceTest.kt:214
#18 2861.8
#18 2861.8 id.walt.services.vc.WaltIdJwtCredentialServiceTest > testValidateSchema FAILED
#18 2861.8     io.kotest.assertions.AssertionFailedError at WaltIdJwtCredentialServiceTest.kt:130
#18 2868.6
#18 2868.6 320 tests completed, 13 failed, 17 skipped
#18 2869.6
#18 2869.6 > Task :test FAILED
#18 2869.6
#18 2869.6 FAILURE: Build failed with an exception.
#18 2869.6
#18 2869.6 * What went wrong:
#18 2869.6 Execution failed for task ':test'.
#18 2869.6 > There were failing tests. See the report at: file:///opt/build/reports/tests/test/index.html
#18 2869.6
#18 2869.6 * Try:
#18 2869.6 > Run with --stacktrace option to get the stack trace.
#18 2869.6 > Run with --info or --debug option to get more log output.
#18 2869.6 > Run with --scan to get full insights.
#18 2869.6
#18 2869.6 * Get more help at https://help.gradle.org
#18 2869.6
#18 2869.6 BUILD FAILED in 47m 48s
#18 2869.7 12 actionable tasks: 11 executed, 1 up-to-date
#18 ERROR: executor failed running [/bin/sh -c ./gradlew clean build]: exit code: 1
------
 > [walt-build 2/3] RUN ./gradlew clean build:
------
executor failed running [/bin/sh -c ./gradlew clean build]: exit code: 1
Service 'ssi-core-dev-env' failed to build : Build failed

I was also facing some other issues on docker as mentioned in this bug https://github.com/walt-id/waltid-ssikit/issues/184 but after changing the line endings in .pem files in test resources and in gradlew files, some issues disappeared but these tell cases still fail. I have converted from Windows-style to UNIX-style line endings in the following files:

gradlew
gradlew.bat
src/test/resources/key/ed25519.pem
src/test/resources/key/pubKeyEd25519.pem
src/test/resources/key/rsa.pem
src/test/resources/key/secp256k1.pem

Can anyone guide me how to fix these issues?

I was following this tutorial and the did:ebsi registration is not work.

[root@baustem ebsi]# ssikit essif did register --did did:ebsi:zgNnvDuBntqiA7eWPZ52HEn#af5dd2f235bd4707bbe2d13fb0ae9f6c walt.id SSI Kit 1.11.0-SNAPSHOT (running on Java 17.0.2+8-86)

EBSI ledger registration for DID did:ebsi:zgNnvDuBntqiA7eWPZ52HEn#af5dd2f235bd4707bbe2d13fb0ae9f6c running...

Could not register DID (after 6 tries to contact EBSI)!

Dear @philpotisk and @severinstampler , I added a new type of VC template for the signatory. There might be errors in it, but I have to start somewhere, right? ;) Would this roughly work out, would love to test it.

I'm trying to extend from SunCryptoProvider and get ...

java.lang.ClassCastException: class id.walt.services.context.ContextManager$Companion cannot be cast 
to class id.walt.servicematrix.ServiceProvider (id.walt.services.context.ContextManager$Companion 
and id.walt.servicematrix.ServiceProvider are in unnamed module of loader 'app')

This is a maven project with ...

        <version.waltid.servicematrix>1.1.2</version.waltid.servicematrix>
        <version.waltid.ssikit>1.13.0-SNAPSHOT4</version.waltid.ssikit>

        <kotlin.compiler.languageVersion>1.8</kotlin.compiler.languageVersion>
        <kotlin.compiler.apiVersion>1.8</kotlin.compiler.apiVersion>
        <kotlin.compiler.jvmTarget>16</kotlin.compiler.jvmTarget>

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /opt/homebrew/Cellar/maven/3.8.6/libexec
Java version: 18.0.2.1, vendor: Azul Systems, Inc., runtime: /Library/Java/JavaVirtualMachines/zulu-18.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "13.0.1", arch: "aarch64", family: "mac"

It shows in IntelliJ and with mvn install

Any idea how this could be fixed

After importing a DID from a file through the CLI tool and executing essif onboard command, an exception is raised "Could not find key". Apparently, the root cause for this issue is that an alias for the did + "#" + kid is created in the did create command but not in the did import method.

The GET method returns 404 every time it's called.

To reproduce the bug, you can:

1. store a credential calling /credential/{alias}
2. call /credentials and see the list, with the new credential just added
3. call /credentials/listCredentialIds and returns 404

It should return the ids of all credentials I know, so at least the last one I've stored.

The PR adds the ability to load templates for VerifiableCredentials from the filesystem. The path can be configured in the signatory.conf. Since the already packaged templates are loaded from the resources inside the jar-file, they cannot easily be extended on deployment or runtime. The changes are non-breaking and therefor backward compatible.

Environment: Docker Desktop with WSL

I'm using the generally available rest-apis on https://docs.walt.id/v/ssikit/getting-started/rest-apis

ISSUE

I'm using the below API and get the below error.

The file below contains the request_body, I tried with both VC and VP in the credentials. and I'm using the format as per https://docs.walt.id/v/ssikit/getting-started/rest-apis/auditor-api vc.txt

WHAT ELSE I TRIED (This lead to other issues)

I tried core API https://core.ssikit.walt.id/v1/vc/verify to verify it, and it works fine, but I can't apply a policy here.

I tried CLI as well...

See the output of the below commands

• ssikit did list

walt.id SSI Kit 1.13.0-SNAPSHOT (running on Java 19.0.1+10)

Listing DIDs...

Results:

1: did:key:z6MkrNhdvrsyBUSsioTnbr9W1iJGT49XxpoNQgShRCqfUmWM 2: did:key:z6MkiFRREdnq6wcDoHA4cYnavgXfG9s9sJY8pTrxX9cuWdro

• ssikit vc issue -i did:key:z6MkrNhdvrsyBUSsioTnbr9W1iJGT49XxpoNQgShRCqfUmWM -s did:key:z6MkiFRREdnq6wcDoHA4cYnavgXfG9s9sJY8pTrxX9cuWdro -t VerifiableId temp.json

Output in file: temp.txt

It says saved to file temp.json, but this file doesn't exist anywhere. I checked the data folder and everywhere else still couldn't find it. Therefore I copied and pasted the generated credentials into a file and ran below command

• ssikit vc verify temp.json

walt.id SSI Kit 1.13.0-SNAPSHOT (running on Java 19.0.1+10)

Verifying from file "temp.json"...

Could not load file: "temp.json".

I tried giving the full path of the file, still it doesn't work