[JIRA] (JENKINS-35249) Security update 1.651.2 breaks LDAP/AD look up

2016-06-23 Thread andrea.curt...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrea Curtoni commented on  JENKINS-35249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Security update 1.651.2 breaks LDAP/AD look up   
 

  
 
 
 
 

 
 I'm experiencing the same problem. Sometimes builds fail after the last step of the actual build. The piece of cause causing trouble seems to be: https://github.com/jenkinsci/jenkins/blob/jenkins-2.6/core/src/main/java/hudson/model/User.java#L1050 It looks like the exception "org.acegisecurity.BadCredentialsException" is not catched (on purpose probably). A possible workaround may be adding JENKINS_JAVA_OPTIONS="-Dhudson.model.User.SECURITY_243_FULL_DEFENSE=false" into /etc/sysconfig/jenkins. I'm not sure it works, testing it right now. However it is not clear which credentials are "Bad". Are these LDAP credentials used to bind to the LDAP server? Why this is not happening constantly but still frequently?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content

2012-11-16 Thread andrea.curt...@gmail.com (JIRA) 














































Andrea Curtoni
 commented on  JENKINS-14551


an update which contains added files merged from a branch results in those files having doubled content















Same issue: Jenkins 1.489, Jenkins Subversion Plug-in 1.43 (it was already bugged in previous versions)



























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