[ 
https://issues.jenkins-ci.org/browse/JENKINS-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162312#comment-162312
 ] 

Samu Wikstedt commented on JENKINS-13600:
-----------------------------------------

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.

                
> 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

        

Reply via email to