Credential|ssuerLD plugin not installed error with jwt-vc

[shihjay2]

After completing successful credential offer, token request, and credential issuance, I get this error. The credential is a jwt-vc format.

[shihjay2]

I'm following up on this since I did not receive any help on this particular issue that came up. I was able to solve part of the problem on my own since the dedicated support line did not respond to my inquiry even with the ticket number. In case others had the same problem, I'll share my solution.

Context

• I used SpruceID DIDKit with my open-source project to generate DIDs for a Verfiable Credential provider project starting in 2022.
• This was working properly including Verifiable Presentations with Sphereon Mobile Wallet when users were needing to present the Verfiable Credential they received from the VC provider when using a GNAP authentication server to present claims.
• Fast forward to 12/2024 after retesting the workflow, errors began to appear on the mobile wallet app as described in the original post.
• I was not able to identify any issues with the VC workflow despite some object/metadata changes but noted the use of Veramo for DID generation/verfication in this app.
• I overhauled my own project to use Veramo for DID generation and signing of the JWT and I was able to complete the VC generation and acquisition by the Wallet. I'm not sure why there is a difference between the DIDKIt and Veramo project but that was the sole change that was made that eliminated the error screen above.

New issue

• Moving on to Verifiable Presentations to the GNAP server, I ran in to a similar error (the GNAP server was also using DIDKit) during the relying party request phase.

• I overhauled my GNAP server code to using Veramo

• But now I keep running into this error:
  

• Looking at this error code, I see that it's related to this extension that is used to buiild the wallet

• In the JWT shared during the relying party request, there is no mention/value of an identifier (just did:key addresses) so I believe this is something related to the wallet not finding an identifier as I believe it's in the process of generating an Authorization Request in SIOPV2 and it's missing or misdeclaring an identifier since the wallet is also using Veramo.

• I used the Dedicated Support line earlier before postiing this response several times without any response to this latest inquiry so I apologize in advance if I'm using the wrong forum for getting help but I'm unable to move forward with troubleshooting what has changed with the workflow since it was successfully implemented since 2022 until now.. Thank you.

[nklomp]

hi @shihjay2 Please be aware that it is the holiday season and most of our staff is on holiday. Next week most people should be back and then we should also have a response for you.

Thanks for the patience.

[nklomp]

Also using this repo / tickets is fine. The "dedicated support" response was a scam, so don't use it. Unfortunately when you are in the identify space, people try to scam others.