Support HMAC SHA256 request signing in the http client #285
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.
Adds optional HMAC SHA256 signing to the HTTP client.
A new HMACRoundTripper (in http/hmac.go) computes and adds a signature for outgoing webhooks. The signature is computed from the request body.
Optionally, a timestamp header name can be specified, and if it's set, the signature is computed from
{timestamp}:{body}
, and the timestamp is added to the headers for the client to verify.Other implementation examples:
Draft PR to Grafana: grafana/grafana#100960 if you want to test it locally.
Part of https://github.com/grafana/alerting-squad/issues/1040