Webhook listener returns a 401
I'm trying to setup a GitHub webhook listener but it seems to return a 401
I also tried setting up a webhook from scratch (without using the GitHub app), and that leads to the same issue
0
I'm trying to setup a GitHub webhook listener but it seems to return a 401
I also tried setting up a webhook from scratch (without using the GitHub app), and that leads to the same issue
Comments
Sagar Vrajalal is your flow on? The flow has to be enabled to get 2XX responses back.
Hi Tyler Lamparter
I enabled the flow now, but I still get the same issue.
I only have the source setup (no destination), because I want to test the webhook listener in isolation. Would this be causing the problem?
So I have now setup the destination and made sure the flow is on, but the 401 still persists.
It looks like this might be related to
https://docs.celigo.com/hc/en-us/community/posts/27093343137563-Enhancement-Request-HMAC-Auth
GitHub prefixes "sha256=" to the signature header which is what seems to cause the issue. Is this something that's being looked at?
It makes the GitHub webhook listener unusable.
Hi Sagar,
I apologize for the inconvenience caused. As I write this, my Engineering team is actively looking into the issue, and we’ll provide a resolution soon. I’ll keep you updated on the progress.
Thanks,
Om Mishra
Om Mishra Small update
I got this to work albeit in a hacky way. I first configured a webhook from scratch instead of using the GitHub one
Then, I created a webhook forwarder API in my application that forwards the headers and the payload to Celigo's webhook url (after stripping the `sha256=` prefix from the `X-Hub-Signature-256` header).
I hope this helps your team in debugging the issue.
This works for me for testing purposes but I do look forward for an update from your side on a permanent fix to this.
Please sign in to leave a comment.