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

Securing Remote Triggers with tokens not working

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • other
    • None
    • Platform: All, OS: All

      Configuration: Hudson is configured for internal user authentication,
      matrix-based security.

      As per bug 1555, if anonymous does not have overall read permission in addition
      to job/build, then remote trigger does not work, with or without token.

      If token is configured on a job, and anonymous is granted overall/read and
      job/build rights (bug 1555 - read access required to trigger remote build), the
      job can be built without a token - job/JOBNAME/build will build (no need for
      ?token=xyz).

      Hudson version 1.184

            Unassigned Unassigned
            brettcave brettcave
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: