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

Trigger builds throws AccessDeniedException

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Hudson version: 1.389
      JDK: 1.6
      OS: RHEL4
    • Similar Issues:

      Description

      When we have Token set in job configuration at "Trigger builds remotely" section I cant trigger build manualy i get AccessDeniedException probably due fix: http://hudson.361315.n4.nabble.com/-td3069369.html

        Attachments

          Issue Links

            Activity

            Hide
            mwebber Matthew Webber added a comment -

            I also have this problem, which is there in 1.389, but was not in 1.384. Here's my description (as sent to the mailing list):

            If you use build triggers with tokens, be aware there is an issue in 1.389.

            I click the "build" icon, and get taken to a web page that says "Access Denied. Invalid token provided.". The console log for Hudson shows:

            [webapp 2010/12/16 12:33:34] - While serving http://<hudson-master>:8080/job/<jobname>/build: org.acegisecurity.AccessDeniedException: Invalid token provided.
            

            This happens for some jobs and not others. According to the job permissions, I should be able to start the build, and this worked in prior versions. The factor in common for the jobs that say "Invalid token provided" is that they all have the "Trigger builds remotely (e.g., from scripts)" build trigger configured (sometimes they have other build triggers also), with a token specified.

            Show
            mwebber Matthew Webber added a comment - I also have this problem, which is there in 1.389, but was not in 1.384. Here's my description (as sent to the mailing list): If you use build triggers with tokens, be aware there is an issue in 1.389. I click the "build" icon, and get taken to a web page that says "Access Denied. Invalid token provided.". The console log for Hudson shows: [webapp 2010/12/16 12:33:34] - While serving http://<hudson-master>:8080/job/<jobname>/build: org.acegisecurity.AccessDeniedException: Invalid token provided. This happens for some jobs and not others. According to the job permissions, I should be able to start the build, and this worked in prior versions. The factor in common for the jobs that say "Invalid token provided" is that they all have the "Trigger builds remotely (e.g., from scripts)" build trigger configured (sometimes they have other build triggers also), with a token specified.
            Show
            sogabe sogabe added a comment - Fixed in 1.391. https://github.com/hudson/hudson/commit/c2c5d1951cc237f6d80566e83a137a96a1c6ea1a

              People

              Assignee:
              sogabe sogabe
              Reporter:
              thunderek thunderek
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: