You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing OpenID4VP with the Sphereon wallet, I noticed that the signer of the JWT (vp_token) is a did:key DID (from the mobile wallet), while the holder (credentialSubject.id) of the contained VC is a did:jwk. How would one ever validate that the signer possesses the private key of the credential subject, if signer != credential subject? Or am I missing something here?
In the example below, the signer of the VP is did:key:z6MksEyx6d5pB1ekoaVmaGsibbcYHE9Vxx7V13PSqPwxYRzL (ed25519 key) and the subject of the VC is did:jwk:eyJhbGciOiJFUzI1NksiLCJ1c2UiOiJzaWciLCJrdHkiOiJFQyIsImNydiI6InNlY3AyNTZrMSIsIngiOiJjMVdYczdXM215c2VVZk5CcXN4ZFBXQklHaEtkNFR6MExSLUZqOEZNWWEwIiwieSI6Ildta0NYdTF3eXpaZ0dON1V4TmFwcHFuT1FhT2tXMkNnT1NuT295TUlUdWMifQ (secp256k1 key).
Thanks for reporting. This is indeed a bug in latest version. Should be fixed in a new release which will have preliminary support for oid4vp v18 as well
While testing OpenID4VP with the Sphereon wallet, I noticed that the signer of the JWT (vp_token) is a
did:key
DID (from the mobile wallet), while the holder (credentialSubject.id
) of the contained VC is adid:jwk
. How would one ever validate that the signer possesses the private key of the credential subject, if signer != credential subject? Or am I missing something here?In the example below, the signer of the VP is
did:key:z6MksEyx6d5pB1ekoaVmaGsibbcYHE9Vxx7V13PSqPwxYRzL
(ed25519 key) and the subject of the VC isdid:jwk:eyJhbGciOiJFUzI1NksiLCJ1c2UiOiJzaWciLCJrdHkiOiJFQyIsImNydiI6InNlY3AyNTZrMSIsIngiOiJjMVdYczdXM215c2VVZk5CcXN4ZFBXQklHaEtkNFR6MExSLUZqOEZNWWEwIiwieSI6Ildta0NYdTF3eXpaZ0dON1V4TmFwcHFuT1FhT2tXMkNnT1NuT295TUlUdWMifQ
(secp256k1 key).JWT:
Decoded JWT headers:
Decoded VC:
The text was updated successfully, but these errors were encountered: