-
Notifications
You must be signed in to change notification settings - Fork 25
Open
Description
Wallet is encrypting the c_nonce value as a JWE using RSA-OAEP-256,
but the Credential Issuer does not publish any RSA encryption key in its metadata.
We need clarification on:
- Whether nonce encryption is required by your wallet implementation
- Where the wallet obtains the RSA public key for this encryption
Steps to Reproduce
- Issuer publishes metadata with only EC signing key
- Wallet calls
/nonceendpoint, receives plain textc_nonce - Wallet encrypts
c_nonceas JWE using RSA-OAEP-256 - Wallet sends proof JWT with encrypted nonce
Expected Behavior
Wallet should either:
- Use the plain text
c_nonceas provided by the Issuer,
or - Encrypt it using a key published in Issuer metadata (.well-known/openid-credential-issuer, if encryption is required)
Actual Behavior
Wallet encrypts the c_nonce without a known public key,
making the Issuer unable to decrypt and verify the proof.
Thanks for support.
Metadata
Metadata
Assignees
Labels
No labels