Add support for HMAC-SHA256 signatures - #40
Merged
Merged
Conversation
Contributor
Author
|
Some API providers (example) recommend or require SHA256 instead of the commonly used SHA1. I'd have a slight preference for re-using the same HMACSigner and adding an algorithm field, but this would be more intrusive. Might break some existing code? |
Owner
|
Thanks |
bvuong
pushed a commit
to fuse-inventory/oauth1
that referenced
this pull request
Sep 16, 2021
* Add a HMAC256Signer
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
New signer for HMAC-SHA256 signatures.
HMAC-SHA1 remains the default for new Authers, HMACSigner struct is unchanged.