Support Asymmetric Signing (especially RS256) in V2 #68
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
abatishchev
force-pushed
the
v2-rs256
branch
from
092d128 to
ed2b5b4
Compare
…dding Json.Net, JsonNetSerializer. Updating nuget packages for Tests
… Sealing all classes but exceptions.
abatishchev
force-pushed
the
v2-rs256
branch
2 times, most recently
from
348c1a4 to
7627e5a
Compare
|
Merged. Published to NuGet as ver. 2.1.0 beta. |
|
👍 |
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.
Adding the support of RS256 using X509Certificate2.