We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback from the ISO mdl DC API interop preparation:
The way that keys should be passed in client_metadata / the way that the key in the client_metadata jwks to use for encryption is selected is unclear.
Some verifiers are including use: enc in the encryption jwk, some are not. Some wallets were requiring a key with use:enc, some were not.
I think there's perhaps a general assumption currently that a "normal" style key selection algorithm would be used, something like described in FAPI: https://openid.net/specs/openid-financial-api-part-2-1_0.html#duplicate-key-identifiers but we should be explicit about the expected behaviour.
The text was updated successfully, but these errors were encountered:
kid
No branches or pull requests
Feedback from the ISO mdl DC API interop preparation:
The way that keys should be passed in client_metadata / the way that the key in the client_metadata jwks to use for encryption is selected is unclear.
Some verifiers are including use: enc in the encryption jwk, some are not. Some wallets were requiring a key with use:enc, some were not.
I think there's perhaps a general assumption currently that a "normal" style key selection algorithm would be used, something like described in FAPI: https://openid.net/specs/openid-financial-api-part-2-1_0.html#duplicate-key-identifiers but we should be explicit about the expected behaviour.
The text was updated successfully, but these errors were encountered: