[JIRA] [core] (JENKINS-23356) NTLM Proxy issue - authentication fails

2014-06-09 Thread goodspe...@comcast.net (JIRA)















































Jim Goodspeed
 resolved  JENKINS-23356 as Not A Defect


NTLM Proxy issue - authentication fails
















This turned out to be an issue with our corporate proxy.





Change By:


Jim Goodspeed
(09/Jun/14 5:50 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-23356) NTLM Proxy issue - authentication fails

2014-06-06 Thread goodspe...@comcast.net (JIRA)














































Jim Goodspeed
 created  JENKINS-23356


NTLM Proxy issue - authentication fails















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


07/Jun/14 12:59 AM



Description:


When trying to install new plugins with a Proxy configured I am getting the following error:

SEVERE: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials
org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials

I have checked my credentials many times and have also tried a co-workers credentials.

We started noticing this after installing the Build Failure Analyzer plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer

Not sure if it is really related or not, but wanted to mention it in the event there was a conflict (we are using the MongoDB configuration as part of the plugin).




Environment:


RHEL 6, Oracle JDK 1.7




Project:


Jenkins



Priority:


Major



Reporter:


Jim Goodspeed

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.