[
https://issues.jenkins-ci.org/browse/JENKINS-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162375#comment-162375
]
dogfood commented on JENKINS-13600:
-----------------------------------
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[jenkins_ui-changes_branch
#26|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/26/]
[FIXED JENKINS-13600] API token authentication was broken in 1.461.
(Revision fdaee7eba3eb2e4fae59255138fa70aa5ada19dc)
Result = SUCCESS
Kohsuke Kawaguchi :
[fdaee7eba3eb2e4fae59255138fa70aa5ada19dc|https://github.com/jenkinsci/jenkins/commit/fdaee7eba3eb2e4fae59255138fa70aa5ada19dc]
Files :
* changelog.html
* core/src/main/java/hudson/security/ACL.java
> Cannot access JNLP URL with apiToken after upgrade to 1.461
> -----------------------------------------------------------
>
> Key: JENKINS-13600
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13600
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Reporter: Sidnei da Silva
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
