Issue a VC using JWK DIDs throwing an error

[rukshanfonseka]

I am using a DID JWK and then tried to issue a VerifiableId credential using /v1/credentials/issue but I get this:
{
"details": [],
"status": 500,
"title": "Algorithm RSA not supported",
"type": null
}

How do I issue this VC using DID JWK?

[mikeplotean]

Hi @rukshanfonseka
Issuing with a did:jwk shouldn't be any different from issuing with other DID methods that SSIKit supports.
Could you please provide an example that can be reproduced?

[rukshanfonseka]

I fetched the main branch and built the docker image and ran SSIKit using serve.

API: /v1/credentials/issue
Payload:
{
"templateId": "VerifiableId",
"config": {
     "issuerDid": "did:jwk:eyJrdHkiOiJSU0EiLCJlIjoiQVFBQiIsInVzZSI6InNpZyIsImtpZCI6IjI5OWU5ZTQ0Y2I5ZjQ4MWU5NDMzNTlkYzk1MWI2MGQ1IiwiYWxnIjoiUlMyNTYiLCJuIjoiczk1NWJ1SWJueHBkeldBRlVnUmdESG82UGZaY2c0WmF4MXMwbGZZaW9YTjhvaDBqUFhyTWdaVTJqNUtibnNST2VpSG0wWm1LUGlHV3NBX19ZQ19NaDBieExnN1JtTnFScDB5Z3BmMWN3VTFDSTBqcVI0MlUtd0NLZnNRbmxncG4zaDRCTnpFTkUtYkd1RVdqWWxScnIyMEZMTDA4bVd2b0NEb254MzJxdWR6MmhaZUlBaWpVaUxNNkZ4S3dtTm83ZmJQeXAzN2JnWTVaNXRjSDBkdFNjSGtYcDF1Q2VnWDZrZWI3cVQ5N2FsUHFKdWdIeWQyQTZjZUdTOUNPVkNvZkg2MGlZYXJRZjhBa3RhNXVpTEZERW15cWFHeXpySmxiNmZXQ1RVb0M4cXFHZ29ta0dMdGVBSExJMnZ2aDQyNUZzYzRHZjJLMDRqbW5OeE4zVFJWZmZuUDN2S2ZheGJPcXJ6ajd2S0ZrLTk3X0NlVXhXT2Jmc2lLeHMwQVpfYnozUzJ4eTRBeEhlRzNudVc3a2JYeFFGSl9BbHdVNmJsb1NTTElfendHNkVUME13LThRdDVZWExMdmZrN24yN09DVnZLRmpnd3pqVTQ4UnFvWmFlb1BzcW4tY2JEa1k4SGZOUnhOdnRQOXlNcTcxZTVROFpYTjQzc0tKMEQxSHcwdXIifQ",
     "subjectDid": "did:jwk:eyJrdHkiOiJSU0EiLCJlIjoiQVFBQiIsInVzZSI6InNpZyIsImtpZCI6IjI5OWU5ZTQ0Y2I5ZjQ4MWU5NDMzNTlkYzk1MWI2MGQ1IiwiYWxnIjoiUlMyNTYiLCJuIjoiczk1NWJ1SWJueHBkeldBRlVnUmdESG82UGZaY2c0WmF4MXMwbGZZaW9YTjhvaDBqUFhyTWdaVTJqNUtibnNST2VpSG0wWm1LUGlHV3NBX19ZQ19NaDBieExnN1JtTnFScDB5Z3BmMWN3VTFDSTBqcVI0MlUtd0NLZnNRbmxncG4zaDRCTnpFTkUtYkd1RVdqWWxScnIyMEZMTDA4bVd2b0NEb254MzJxdWR6MmhaZUlBaWpVaUxNNkZ4S3dtTm83ZmJQeXAzN2JnWTVaNXRjSDBkdFNjSGtYcDF1Q2VnWDZrZWI3cVQ5N2FsUHFKdWdIeWQyQTZjZUdTOUNPVkNvZkg2MGlZYXJRZjhBa3RhNXVpTEZERW15cWFHeXpySmxiNmZXQ1RVb0M4cXFHZ29ta0dMdGVBSExJMnZ2aDQyNUZzYzRHZjJLMDRqbW5OeE4zVFJWZmZuUDN2S2ZheGJPcXJ6ajd2S0ZrLTk3X0NlVXhXT2Jmc2lLeHMwQVpfYnozUzJ4eTRBeEhlRzNudVc3a2JYeFFGSl9BbHdVNmJsb1NTTElfendHNkVUME13LThRdDVZWExMdmZrN24yN09DVnZLRmpnd3pqVTQ4UnFvWmFlb1BzcW4tY2JEa1k4SGZOUnhOdnRQOXlNcTcxZTVROFpYTjQzc0tKMEQxSHcwdXIifQ"
},
"credentialData": {
     "credentialSubject": {
         "name": "Rukshan"
         }
     }
}

Response:
{
  "details": [],
  "status": 500,
  "title": "Algorithm RSA not supported",
  "type": null
}

There is an exception in SSIKit:

[JettyServerThreadPool-58] ERROR id.walt.services.jwt.WaltIdJwtService - Algorithm RSA not supported
[JettyServerThreadPool-58] ERROR id.walt.signatory.rest.SignatoryRestAPI - java.lang.UnsupportedOperationException: Algorithm RSA not supported
        at id.walt.services.jwt.WaltIdJwtService.sign(WaltIdJwtService.kt:142)
        at id.walt.services.jwt.JwtService.sign(JwtService.kt:30)
        at id.walt.services.jwt.JwtService.sign(JwtService.kt:36)
        at id.walt.sdjwt.SDJwt$Companion.sign(SDJwt.kt:203)
        at id.walt.sdjwt.SDJwt$Companion.sign$default(SDJwt.kt:201)
        at id.walt.services.vc.WaltIdJwtCredentialService.sign(WaltIdJwtCredentialService.kt:68)
        at id.walt.services.vc.JwtCredentialService.sign(JwtCredentialService.kt:15)
        at id.walt.signatory.WaltIdSignatory.issue(WaltIdSignatory.kt:122)
        at id.walt.signatory.WaltIdSignatory.issue(WaltIdSignatory.kt:92)
        at id.walt.signatory.rest.SignatoryController.issueCredential(SignatoryController.kt:91)
        at id.walt.signatory.rest.SignatoryRestAPI$start$2$3$1$1.invoke(SignatoryRestAPI.kt:123)
        at id.walt.signatory.rest.SignatoryRestAPI$start$2$3$1$1.invoke(SignatoryRestAPI.kt:123)
        at io.javalin.plugin.openapi.dsl.OpenApiBuilder.documented$lambda-0(OpenApiBuilder.kt:23)
        at io.javalin.plugin.openapi.dsl.DocumentedHandler.handle(DocumentedHandler.kt:10)
        at io.javalin.core.security.SecurityUtil.noopAccessManager(SecurityUtil.kt:20)
        at io.javalin.http.JavalinServlet.addHandler$lambda-0(JavalinServlet.kt:96)
        at io.javalin.http.JavalinServlet$lifecycle$2$1$1.invoke(JavalinServlet.kt:43)
        at io.javalin.http.JavalinServlet$lifecycle$2$1$1.invoke(JavalinServlet.kt:43)
        at io.javalin.http.JavalinServletHandler.executeNextTask(JavalinServletHandler.kt:99)
        at io.javalin.http.JavalinServletHandler.queueNextTaskOrFinish$lambda-1(JavalinServletHandler.kt:85)
        at java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1187)
        at java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2341)
        at io.javalin.http.JavalinServletHandler.queueNextTaskOrFinish$javalin(JavalinServletHandler.kt:85)
        at io.javalin.http.JavalinServletHandler.executeNextTask$lambda-11$lambda-10(JavalinServletHandler.kt:119)
        at java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:684)
        at java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:662)
        at java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2200)
        at io.javalin.http.JavalinServletHandler.executeNextTask(JavalinServletHandler.kt:119)

[rukshanfonseka]

Note that if I use the SSIKit command line the VC is generated fine, but I do want to use the REST APIs as I am not sure how to change the suject's data using the command line.

[mikeplotean]

Thank you for providing the issue details. Seems like the signing with RSA was missing for JWT credential format (for the REST API - the default is proofType = JWT, while for command-line interface it is proofType=LD_PROOF - the reason why it worked for cli).
This is fixed now and should be available.

About updating credential template properties (e.g. subject data) from command-line interface, it is possible with the --interactive option:

ssikit vc issue -t VerifiableId -s <your-subject-did> -i <your-issuer-did> --interactive

More details can be found in the Verifiable Credentials section from docs.
However, one thing to keep in mind: interactive mode is available only for static (pre-defined) credentials. For a custom credential template, you'll have to implement a custom data-provider.