You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm trying to create a Jira automation that sends a web request to an API endpoint and adds the response to the original issue.
I know my request should work(I tested it both with python requests and burp), but when I run it via Jira I get the following error -
<Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.</Message>
I even went as far as setting up my own server to see exactly what the request looks like once It's out of Jira, and replicated it with all the additional headers I did not specify. It worked for me to run the request manually.
From everything I've read, It seems that the problem is that the signature is calculated before the squid proxy adds additional headers, and with said additional headers the old signature is no longer valid....
I have no control over the proxy or the calculation of the signature so I'm a bit lost for a solution and will appreciate any input :)
Hi @Dina Teper , welcome to the Community!
This sounds like an interesting situation. Are you able to share some more information about the service receiving the webhook, and confirm you're on Jira Cloud (url like "yoursite.atlassian.net") vs an on-prem instance (url like "jira.yourdomain.com")? Jira Cloud doesn't use squid proxy in its outbound requests, so I'm interested to know where this additional piece is.
Daniel | Atlassian Support