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

Cannot access JNLP URL with apiToken after upgrade to 1.461

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None

      Description

      Accessing the JNLP URL on an OpenID-protected instance does not work anymore after upgrading to 1.461. Reverting to 1.459 makes it work again.

      Error with 1.461:

      Exception: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@9f6d50cd: Username: hal; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities

      To test:

      curl -kinsecure -u user:apitoken https://localhost/computer/computer-name/slave-agent.jnlp

        Activity

        sidnei Sidnei da Silva created issue -
        Hide
        sidnei Sidnei da Silva added a comment -

        FWIW, sounds like a similar issue to JENKINS-11562, though I haven't tried to dig into the source yet.

        Show
        sidnei Sidnei da Silva added a comment - FWIW, sounds like a similar issue to JENKINS-11562 , though I haven't tried to dig into the source yet.
        Hide
        scm_issue_link SCM/JIRA link daemon added a comment -

        Code changed in jenkins
        User: Kohsuke Kawaguchi
        Path:
        changelog.html
        core/src/main/java/hudson/security/ACL.java
        http://jenkins-ci.org/commit/jenkins/fdaee7eba3eb2e4fae59255138fa70aa5ada19dc
        Log:
        [FIXED JENKINS-13600] API token authentication was broken in 1.461.

        Show
        scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/security/ACL.java http://jenkins-ci.org/commit/jenkins/fdaee7eba3eb2e4fae59255138fa70aa5ada19dc Log: [FIXED JENKINS-13600] API token authentication was broken in 1.461.
        scm_issue_link SCM/JIRA link daemon made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        dogfood dogfood added a comment -

        Integrated in jenkins_main_trunk #1685
        [FIXED JENKINS-13600] API token authentication was broken in 1.461. (Revision fdaee7eba3eb2e4fae59255138fa70aa5ada19dc)

        Result = SUCCESS
        Kohsuke Kawaguchi : fdaee7eba3eb2e4fae59255138fa70aa5ada19dc
        Files :

        • changelog.html
        • core/src/main/java/hudson/security/ACL.java
        Show
        dogfood dogfood added a comment - Integrated in jenkins_main_trunk #1685 [FIXED JENKINS-13600] API token authentication was broken in 1.461. (Revision fdaee7eba3eb2e4fae59255138fa70aa5ada19dc) Result = SUCCESS Kohsuke Kawaguchi : fdaee7eba3eb2e4fae59255138fa70aa5ada19dc Files : changelog.html core/src/main/java/hudson/security/ACL.java
        Hide
        swiksted Samu Wikstedt added a comment -

        Hi,

        is this same bug affecting API functionality as a whole? Not just when using openID plugin? We are using LDAP authentication and have experiencing problems after After upgrading to 1.461, and upgrading to 1.462 didn't fix this.

        (parametrized)Jenkins projects are builded trough API like this:
        swiksted@xxxxxxxx:~$ wget --no-proxy --auth-no-challenge --http-user=swiksted --http-password=users_api_token http://xxxx.xxxx.xxxx/job/projectname/buildWithParameters? --post-data="param=value&another_param=another_value"

        -2012-05-02 10:25:14- http://xxx.xxx.xxx/job/project_name/buildWithParameters?
        Resolving xxx.xxx.xxx... xxx.xxx.xxx.xxx
        Connecting to xxx.xxx.xxx|xxx.xxx.xxx.xxx|80 failed: Connection refused.

        Show
        swiksted Samu Wikstedt added a comment - Hi, is this same bug affecting API functionality as a whole? Not just when using openID plugin? We are using LDAP authentication and have experiencing problems after After upgrading to 1.461, and upgrading to 1.462 didn't fix this. (parametrized)Jenkins projects are builded trough API like this: swiksted@xxxxxxxx:~$ wget --no-proxy --auth-no-challenge --http-user=swiksted --http-password=users_api_token http://xxxx.xxxx.xxxx/job/projectname/buildWithParameters? --post-data="param=value&another_param=another_value" - 2012-05-02 10:25:14 - http://xxx.xxx.xxx/job/project_name/buildWithParameters? Resolving xxx.xxx.xxx... xxx.xxx.xxx.xxx Connecting to xxx.xxx.xxx|xxx.xxx.xxx.xxx|80 failed: Connection refused.
        Hide
        dogfood dogfood added a comment -

        Integrated in jenkins_ui-changes_branch #26
        [FIXED JENKINS-13600] API token authentication was broken in 1.461. (Revision fdaee7eba3eb2e4fae59255138fa70aa5ada19dc)

        Result = SUCCESS
        Kohsuke Kawaguchi : fdaee7eba3eb2e4fae59255138fa70aa5ada19dc
        Files :

        • changelog.html
        • core/src/main/java/hudson/security/ACL.java
        Show
        dogfood dogfood added a comment - Integrated in jenkins_ui-changes_branch #26 [FIXED JENKINS-13600] API token authentication was broken in 1.461. (Revision fdaee7eba3eb2e4fae59255138fa70aa5ada19dc) Result = SUCCESS Kohsuke Kawaguchi : fdaee7eba3eb2e4fae59255138fa70aa5ada19dc Files : changelog.html core/src/main/java/hudson/security/ACL.java

          People

          • Assignee:
            Unassigned
            Reporter:
            sidnei Sidnei da Silva
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: