Forbidden - CSRF header not found in request with bitbucket and tekton trigger with webhooks

anandjaisy

I have set up the Tekton Trigger to auto-run the pipeline when certain code is pushed to the bitbucket repository.

 

apiVersion: triggers.tekton.dev/v1beta1
kind: EventListener
metadata:
  name: bitbucket-listener
  namespace: fetebird-common
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: bitbucket-triggers
      interceptors:
        - ref:
            name: "bitbucket"
          params:
            - name: secretRef
              value:
                secretName: git-ssh-key-secret
                secretKey: ssh-privatekey
            - name: eventTypes
              value:
                - repo:refs_changed
      bindings:
        - ref: bitbucket-trigger-binding
      template:
        ref: bitbucket-trigger-template

 

 

<image removed to protect privacy>

 

The details of the webhook

 

<image removed to protect privacy>

 

Error Forbidden - CSRF header not found in the request using the FREE trial version

Ben

Hi Anand,

Thought I would jump in here as you have not received a response yet from our Community.

Based on the webhooks log you have provided - I can see that the error is being returned by Tekton itself and seems to indicate that the headers being sent by Webhooks are not considered valid by Tekton.

We do not have explicit knowledge of Tekton as it is a third-party platform, however - based on Tekton's documentation, I can see that it has a webhooks interceptor specifically made for this purpose: https://tekton.dev/vault/triggers-v0.6.1/eventlisteners/#webhook-interceptors

Additionally, I notice that you are mentioning secrets in your YML configuration - at present, Webhooks does not support secrets although a feature request has been logged to track this with our development team:

• https://jira.atlassian.com/browse/BCLOUD-14683 

Here is an example Webhooks header - Tekton will need to be configured to accept a header such as this, otherwise, it is likely that you will continue to encounter this issue:

Headers
connection Keep-Alive
content-length 8668
x-forwarded-server personal.webhooks
x-forwarded-host personal.webhooks
x-forwarded-for 18.246.31.226
accept */*
x-b3-sampled 1
x-b3-spanid aa8d4ce456223054
x-b3-traceid aa8d4ce456223054
content-type application/json
x-request-uuid a448af67-3068-4f20-bc32-2325a2edcf92
x-attempt-number 1
user-agent Bitbucket-Webhooks/2.0
x-event-time Thu, 28 Sep 2023 12:27:26 GMT
x-hook-uuid b956df39-eeb6-4fb0-8c0b-146d2c2131a5
x-event-key repo:push
host personal.webhooks

If you still encounter issues - I would suggest reaching out to the Tekton community for further assistance with configuring their platform-specific webhooks interceptor:
https://tekton.dev/community/

Hope this helps steer you in the right direction.

Cheers!

- Ben (Bitbucket Cloud Support)