Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

How to authenticate webhooks?

The webhook documentation and API documentation do not mention how to authenticate a webhook sent to the configured URL. Is there a supported way to do this?

Typically I'd expect a signature to verify or a header with an API key but I don't see either in the requests.

I could hard code an API key into a query param on the configured URL but that seems less than ideal.

Any help would be much appreciated.

1 answer

1 vote
Caroline R
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 09, 2021

Hi, @ben_walford! Welcome to the community! 

If I understood your question correctly, you would like to authenticate the webhook destination servers, is that correct? If that’s the case, unfortunately, we currently don't have a way to do this as this feature is not available yet. We do have a feature request for this as you can see in the link below:

I've linked your question to this feature request. Please consider adding yourself as a watcher, so you get updated as we make progress with this. If you are not familiar with our Feature Request Policy, you can learn more about it here:

So, as a workaround, you can pass the credential using HTTPS by using: 

https://<username>:<Password>@<URL>

Please, feel free to share any additional questions regarding this subject.

Kind regards,
Caroline

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events