Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generic HTTP Connector: OAuth1 supports different signature hashing methods #1324

Open
JakeQuilty opened this issue Aug 6, 2020 · 0 comments

Comments

@JakeQuilty
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Authenticating with OAuth1 to services that use signature hashing methods that aren't HMAC-SHA1 is not possible.

Describe the solution you would like

A parameter in the oauth1 config key that lets the user specify the hash type, or default to HMAC-SHA1 if not specified.
For PLAINTEXT a new header will need to be created that will not use the same format as constructOAuthString(See PLAINTEXT link bellow)

Describe alternatives you have considered

This seems like the only solution since the signature hash method can change between services.

Additional context

HMAC-SHA1 - https://tools.ietf.org/html/rfc5849#section-3.4.2
RSA-SHA1 - https://tools.ietf.org/html/rfc5849#section-3.4.3
PLAINTEXT - https://tools.ietf.org/html/rfc5849#section-3.4.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant