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
Next: Root
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
Background
I want to integrate Bitbucket with Jenkins.
I have made plugin that I want to use.
The plugin supports HMAC and IP filtering, to limit access to it.
Problem
My current workplace has Bitbucket and Jenkins running on different networks with a proxy between. Jenkins will always see same IP from the proxy, so I cannot limit access to IP.
Technically, I could use HMAC. But the secret would have to be configured by a repo administrator, in each repo, and that "secret" is likely to not be a secret for long.
Proposed solution
I found this, listing different properties:
https://confluence.atlassian.com/bitbucketserver/bitbucket-server-config-properties-776640155.html
If there was a property like plugin.webhooks.signature.secret that can be set to a global default secret. Used for signing any webhook unless a secret is given in that repo.
What do you think?
Edit: I created: https://jira.atlassian.com/projects/BSERV/issues/BSERV-12248