Hello,
I have been testing the Dome Wallet and I have found the issue described at this post on discord
The scenario is:
- A VC issued by the keycloak VCIssuer on its version 26.0.5 generates a VC for an user with the following info (dns is a fake one):
openid-credential-offer://?credential_offer_uri=https%3A%2F%2FFAKEDNS%2Frealms%2FFAKEREALM%2Fprotocol%2Foid4vc%2Fcredential-offer%2FPYdg71XDObHnP4En76jO4G64ok4S6zXJ.79d3cc4d-7534-4713-8076-151285ddb56f.35981cd7-d953-4189-b8d6-12a435f0418d
- An Android mobile navigates to the Dome Wallet, logs in and tries to scan the QR code of the previous VC.
- After capturing the QR code with the camera, an error popups on the mobile screen saying We could'nt process the QR code. It might be invalid or already used.
- Both the wallet and the VCIssuer have exchanged some messages shown at the discord thread
But the error seems related with an unknown field refresh_expires_in.
Should the wallet be aware of the new fields published by keycloak as VCIssuer.
Keycloak supports Verifiable Credentials (VC) Issuance primarily through the OpenID for Verifiable Credentials (OID4VC) protocol OpenID for Verifiable Credential Issuance (OID4VCI)
Hello,
I have been testing the Dome Wallet and I have found the issue described at this post on discord
The scenario is:
But the error seems related with an unknown field
refresh_expires_in.Should the wallet be aware of the new fields published by keycloak as VCIssuer.
Keycloak supports Verifiable Credentials (VC) Issuance primarily through the OpenID for Verifiable Credentials (OID4VC) protocol OpenID for Verifiable Credential Issuance (OID4VCI)