-
Notifications
You must be signed in to change notification settings - Fork 17
JWKS: Remove publicKeys in favor of RFC7515. #319
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
base: develop
Are you sure you want to change the base?
Conversation
glpatcern
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is already good, do you think we could provide an example of how to use the jwks.json? Also, at this point I'm ok to keep the deprecated part, but I'd remove the now-fully-outdated example.
I removed the deprecated example now. Where would be a good place to put an example, and how would you like it to be? An example json with the various fields? |
Good question: what about an Appendix as it was done with the previous example? Then yes I'd include an example JSON like the one in #313, and a code snippet from your own toy implementation (it's python IIRC right?) to 1) encode and add a signature at the sender and 2) validate it at the receiver. |
25e4791 to
e390337
Compare
Good thing you mentioned appendices.. We hade appendix b with draft-cavage signature examples. I rewrote that, and I hope it is something what you wanted. A lot of python code didn't look good so a step by step algorithm turned out better I think. |
e390337 to
403ff0a
Compare
Ah yes, that appendix indeed was also obsoleted now, great that you rewrote it. I think the text and the step by step part is good but the |
glpatcern
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So for the code snippets:
There is e.g https://pypi.org/project/http-message-signatures/ but I am not sure that adding snippets using this is really helpful. This is their example: Easy enough to look up when implementing, but not really helping you understand what is going on IMO. |
Well it's not too bad after all, but I take your point that it might be too much to include such code snippets in an Internet Draft. So let's give it try without and we can bring this to the WG anyway. Let me re-review for just a couple of fixes |
glpatcern
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minimal fixes - I think it's better to have abstract values (as in RFC7515 actually), especially without any actual code snippet
- Fix http-sig capability to reference RFC7517 instead of RFC7515 - Add RFC7517 (JWK) and RFC8032 (EdDSA) to references - Fix RFC7515 reference formatting - Replace draft-cavage examples with RFC9421 signature format - Add JWKS endpoint and Ed25519 signing/verification examples Co-authored-by: Giuseppe Lo Presti <giuseppe.lopresti@cern.ch>
e753278 to
ad09853
Compare
Added in them now. |
Fixes: #313