Remote trigger plugin bearer token header is incorrect

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Environment:
      Jenkins parameterized remote trigger plugin 3.2.1

      When triggering a remote job on a Jenkins instance running in OpenShift, authorization with username and password is not supported. Instead, the token of an OpenShift service account needs to be encoded and passed as a bearer token in the `Authorization` header. See the OpenShift Plugin documentation for this: https://plugins.jenkins.io/openshift-login/#plugin-content-non-browser-access .

      However, this bearer token is passed incorrectly via the Authorization header: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/blob/master/src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/auth2/BearerTokenAuth.java#L41

      The value of the header starts with `Bearer:` followed by the token, but should not contain a colon `:`.

            Assignee:
            KaiHsiang Chang
            Reporter:
            Ruben
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: