HiThe x-hub-signature header is still not being received for webhooks created via REST APIs using OAuth access tokens in Jira Cloud, even though a secret was provided. Any help or clarification on this would be greatly appreciated.
x-hub-signature
If possible, please share any official documentation that explains this behavior.Referenced below document.https://developer.atlassian.com/cloud/jira/platform/webhooks/#registering-a-webhook-using-the-rest-api--for-connect-and-oauth-2-0-apps-My API : https://api.atlassian.com/ex/jira/{jira_cloud_id}/rest/api/3/webhookTried Payloads:
Hey @Anand Elumalai
Welcome to Atlassian community!
I will recommend you to reach below team to help you with this issue.
Atlassian Developer and Marketplace support : https://developer.atlassian.com/support
Atlassian Developer Community: https://community.developer.atlassian.com/
RegardsChitra Nagdeo
Took me months to find the answer, so hopefully this helps someone else.
For webhooks created via REST API for oauth 2.0 apps - passing the secret is not required.
The webhook payload comes with an Authorization <token> that is signed using your oauth app client secret. literally all you have to do is check for the token, verify that the signature matches your client secret. Boom security.
Simply put for webhooks created via the admin console, payloads come with X-Hub-Signature, while for webhooks created via Rest API, payloads come with Authorization token, signed with your client secret. My implementation in NestJS
It looks like you're new here. Sign in or register to get started.