Bitbucket Cloud integration with Jenkins 403 no valid crumb

[Cecil Morris]

Using Bitbucket Cloud (not Server) and created a webhook specifying our Jenkins server. The Jenkins server has the Bitbucket Branch Source Plugin installed and configured with the Bitbucket endpoint and credentials for accessing Bitbucket from Jenkins. The webhook executes and I trace the POST through the nginx proxy server to the Jenkins server and back. The reply is a 403 with the message about "no valid crumb". This is because CSRF is turned on in Jenkins global security along with the Defautl Crumb Issuer and proxy compatibility enabled. If I turn off CSRF in Jenkins, then I get a permission denied for anonymous user instead of the "no valid crumb" error. CloudBees has a good description at https://support.cloudbees.com/hc/en-us/articles/219257077-CSRF-Protection-Explained on why/who to create a crumb.

So my question is how to configure the webhook for create and send a valid crumb in the header along with the Bitbucket originated webhook request? According to CloudBees, the crumb expires so it needs to be dynamically generated by the webhook trigger. I don't see any documentation for Bitbucket about handling authentication with webhooks. (Creating a valid crumb requires contacting the Jenkins server with a username/password and a crumb request)

Has anyone successfully used a Bitbucket Cloud webhook to trigger a Jenkins build where Jenkins has authentication configured along with CSRF. Wondering if there is another way to tackle this problem.

Thank you, Cecil

[Cecil Morris · Accepted solution]

Finally found an answer that works for me. I set my webhook URL to the Jenkins server with "/bitbucket-scmsource-hook/notify" and now git push causes Bitbucket to successfully trigger a build in Jenkins. Documented by CloudBees at:

https://support.cloudbees.com/hc/en-us/articles/11500005113-How-to-Trigger-Multibranch-Jobs-from-BitBucket-Cloud-

I tried "/bitbucket-hook/" and that successfully connected to the Jenkins server and returned a 200 status code but Jenkins did not start a build or a scan. Seems that this url works for non-multi-branch jobs.

I am using Mutltibranch Pipline jobs and have the scan set to 1 day. Defining a periodic scan is required per documentation and testing. 

[Srujan Kavane]

The document has been moved to the following link:

https://support.cloudbees.com/hc/en-us/articles/115000051132-How-to-Trigger-Multibranch-Jobs-from-Bitbucket-Cloud-

[mehylander]

I was able to get it to work by rolling the plugin back to the previous version.  I did this after trying all the other posted fixes I found on the web. 

[Eliza Leong]

Could you please share which exact version of the plugin did you use?