Asymmetric keys #129
Open
Asymmetric keys #129
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
Update with examples from HTTP Message Signatures draft 13
add support for JWK in bobcats
* update cats & cats-effect * updated sbt
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.
I am just opening this PR as a place to discuss the commits on asymmetric keys I have been making.
Perhaps we should create a special asymmetric key branch on the repo here to which I can push these changes? That would make discussions on where to go a bit easier.
I need the asymmetric keys for implementing Signing HTTP Messages draft 13 which was in last call. I have this implemented HTTP Sig for Http4s (scala + scalajs) and Akka.
I will need to add JWT support next, and have started a branch and PR for that. PEM is a nightmare (see Issue 2290 of HTTPWG).
JWT support strains the architecture a bit. I wonder for example if we should not move more towards the pattern I have been using to abstract the different RDF frameworks across Java and JS, as described in the into to this post on scala-users...