Skip to content
New issue

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

add support for JWK #54

Open
bblfish opened this issue Jan 4, 2022 · 0 comments
Open

add support for JWK #54

bblfish opened this issue Jan 4, 2022 · 0 comments

Comments

@bblfish
Copy link

bblfish commented Jan 4, 2022

The branch for asymmetric keys #48 allows them to be given by two specifications:

Both of those are usually sent around in a binary ASN.1 encoded form transformed in base64 as PEM documents. The binary encoding makes understanding what is wrong with them quite difficult as shown by bizarre problems such as in issue 1867 for the Signing HTTP Messages spec.

Luckily there are human readable JSON Web Key format that is supported by the Web Crypto API. This is widely used in new web based crypto protocols, and so should really be supported here too. One would then have to add something like the following

  • JWKPublicKeySpec
  • JWKPrivateKeySpec

It is helpful to keep this in mind as that should help in deciding about the public API for Signer and Verifier.

For Java this would I think require using an extra library such as "com.nimbusds" % "nimbus-jose-jwt" used in the demo test JWKCryptoSuite.scala.

If this dependency is problematic one should I guess make a separate project for it so that it can be pulled independently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant