Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-59219

Found invalid crumb

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • core
    • None
    • Windows 2016 server
      Jenkins 2.193
      pull-request-notifier-for-bitbucket 4.1
      Bitbucket 6.4.0

      After upgrading Jenkins from 2.189 to 2.193 due to security issues none of the jobs I have setup in jenkins to be triggered by the pull-request-notifier is started. There are 2 options the way I see it:

      1. some of the changes in Jenkins is breaking the notifier-plugin in Bitbucket, or
      2. the implentation in Jenkins doesn't work as intended.

      None of the configurations of the 20+ jobs I have that is triggered by this plugin have changed.

      Extract from log:
      2019-09-04 08:22:33.903+0000 [id=35] WARNING hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb e55f02079f26ceaa8d7751f38e119adeea156a549c169642bdeeafb4029b0317. Will check remaining parameters for a valid one...
      2019-09-04 08:22:33.903+0000 [id=35] WARNING hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /job/PKING-pm/buildWithParameters by jenkins. Returning 403.

       

            Unassigned Unassigned
            kengra Kent Granström
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: