Method to get JWK from EncodingKey #360
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
My (limited) real world testing worked. Obviously splitting the bytes is a hack, but I wasn't able to find the ring internal methods that extract that data. I may continue to look, but I think this is relatively safe. |
andrewbaxter
changed the title
added 2 commits
January 15, 2024 20:14
|
andrewbaxter#2 targetted at the ACME/JWS branch |
andrewbaxter
force-pushed
the
jwk-from-encoding-key
branch
from
3c89f8d to
dd34b25
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per #357
I excluded Ed25519 for now, but the rest works as expected I believe. I'm going to test it with the code I wanted to use it in originally for now.