Add RSA-SHA1 signing capability #918
Merged
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
added 2 commits
December 23, 2016 23:05
Includes tests with 1024, 2048, and 4096 key sizes, and several values to be hashed/signed.
|
This PR seems to have failed its AppVeyor build although I can't see a reason my commits would be related to it; it's a problem with the RestSharp.UWP.csproj file, which is nothing I touched. |
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.
Supports OAuthSignatureMethod.RsaSha1, useful for integrations with RSA SHA1-based OAuth integrations such as Atlassian JIRA's REST API. I've tested this against my company's JIRA Server 7.2.2 instance, as well as with the unit tests included in the PR.