Skip to content

Some additional notes around webhook signature verification. #101

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Feb 16, 2024
Merged

Some additional notes around webhook signature verification. #101

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f131fe5
Some additional notes around webhook signature verification.
ChuckCrawford Feb 16, 2024
5f2167d
nit.
ChuckCrawford Feb 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/webhooks/04-Signatures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,14 @@ If at least one of the signatures matches, the webhook should be considered a tr
<!-- theme: info -->
> Note: When comparing signatures, be sure to use a constant-time string comparison to protect against timing attacks.

<!-- theme: warning -->
> Verifying PagerDuty webhook signatures requires the unaltered raw body of the request sent to you.
> Ensure that any frameworks or middleware you are using have not manipulated or formatted the request body.

<!-- theme: warning -->
> PagerDuty webhook payloads support unicode characters. If your implementation is converting the request body
> from string to bytes [or vice-versa], ensure that you are using the proper UTF-8 character encoding.

## Examples of webhooks signing

<!--
Expand Down