Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Custom bitbucket webhook secret handling

Hi, I am working with receiving updates from BB on Comments (Added, edited, deleted) and PR Actions (Declined, deleted). 

I am trying to implement a secret on the webhook, however, am inexperienced with doing any sort of cryptography. My understanding is that I need to take the message body and encrypt it using HMACSha256 with the secret as the key and that should equal the value in the "X-Hub-Signature" header. (here) However, when I try this I do not end up with the same values. What is the format that we are expected to use for the body when encrypting it?


I am having a hard time discerning if my trouble is being caused by my incompetence in encrypting it or my incompetence in formatting the body correctly.


I am currently trying to use the value directly given from the request on BB on a single line, with no newlines. 


Does anyone have any experience with this that can point me in the right direction?

0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events