openwallet-foundation / openwallet-foundation/acapy-plugins
OID4VC: demo is not working properly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 47
- Avg merge
- 13h 22m
- Merged PRs (30d)
- 12
Description
I'm experiencing an issue while following the steps described in oid4vc/README.md. After selecting the SD-JWT VC format and filling in all the values, I tried to read credentials using the Sphereon wallet, but the wallet freezes during this process and only displays a blank page.
I can see some activity in the webhooks, which suggests that there is communication between the issuer node app and the wallet. However, the Sphereon wallet fails to display any credential information and becomes unresponsive when trying to process the credentials from the issuer.
This is particularly confusing because I have successfully run the OID4VC demo in the past, where I was able to issue credentials and read them properly in the Sphereon wallet without any issues. I'm wondering if there have been any recent changes to the OID4VC plugin that might affect wallet compatibility, or if there are specific versions of the Sphereon wallet (or any wallet) that are known to work reliably with the current plugin version. Any guidance on additional debugging steps or logs that might help diagnose this issue would be greatly appreciated, as I'd like to get this working again as it did previously.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with oid4vc/README.md and reproduce the SD-JWT VC flow using the Sphereon wallet. Inspect the issuer node app's webhook activity and available logs to identify where credential processing stops; done means the wallet displays the issued credential without freezing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100