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.

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

Jump to bottom

Support for HMAC-signed hook payloads #9

Open
delroth opened this issue Aug 30, 2015 · 0 comments
Open

Support for HMAC-signed hook payloads #9

delroth opened this issue Aug 30, 2015 · 0 comments

Comments

@delroth
Copy link

delroth commented Aug 30, 2015

Webhook URLs are usually exposed over the internet, so a common practice in webhook modules is to provide the ability for the user to specify a shared secret (hmac key) that is used to sign the payload when sending it to the webhook URL. This authentifies the origin of the payload to its recipient.

I couldn't find anything like that in redmine_webhook unfortunately. I might work on this in the future, but still filing this feature request in case someone else has more time than I do :)
ricekab added a commit to ricekab/redmine_webhook that referenced this issue Oct 23, 2022
@ricekab
NEW: (suer#9) Added secret_key to webhooks . Post now includes HMAC v…
8c3fb0c 
…erification

signature.

Currently this is hard-coded to use sha1, this should be made configurable on a global or project basis. (Or perhaps even per hook?).

Direct link to upstream issue: suer#9
@ricekab ricekab mentioned this issue Oct 23, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@delroth