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 have added bitbucket webhook for jenkins integration in my repository settings but it is returning 403 error. The webhook URL is provided in the following format:
The username provided also have admin access in Jenkins still it is giving :
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access /bitbucket-hook/ on this server.<br /> </p> </body></html>
I have tried all the combinations like username:password instead of API token but it is throwing error in all conditions.
Just to let you know that Jenkins can successfully pull the code from bitbucket when the job is triggered manually.
The 403 status is actually pretty descriptive here: it means that user doesn't have permission to that endpoint (/bitbucket-hook). The network is fine (otherwise you would get a NET_ERR), and the credentials themselves are OK (otherwise you would get a 401), and there's an endpoint by that name (otherwise you would get a 404), but the user in question is just not allowed to do that action.
You should examine the listener's configuration on Jenkins - that's where the issue appears to be. Look especially for user permissions.
I've used both privileged and non privileged users and every time I get the 403.
In my case, I'm able to use the same url (https://username:apitoken@jenkins-url/webhook-url-params/) in an older version of GitLab and the webhook works.