[JIRA] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
Rick Liu commented on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 I believe this issue is the same as JENKINS-22727 AD plugin times out for large user/group membership. 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
Alex Lombardi edited a comment on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 Seeing the same issue on both a W2K3 and a W2K8 device. Noticed that a backup instance of the active-directory.jpi named active-directory.bak now exists with the old data. When I renamed the new jpi something else and made the backup active all worked well, but the system detected an update was again available which caused the same issue. 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
Alex Lombardi edited a comment on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 Seeing the same issue on both a W2K3 and a W2K8 device. Noticed that a backup instance of the active-directory.jpi named active-directory.bak now exists with the old data. When I renamed the new jpi something else and made the backup active all worked well, but the system detected an update was again available which caused the same issue. Running Jenkins as a Windows service with java 1.8 on the device. Domain names added to the configurations. 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
podskalsky commented on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 I have the same problem an my Solaris(sparc) system 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
podskalsky edited a comment on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 I have the same problem at my Solaris(sparc) system 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
Rick Liu created JENKINS-22669 login failed after upgrade to 1.37 from 1.36 Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: active-directory-1.36-ok.log, active-directory-1.37-err.log Components: active-directory Created: 17/Apr/14 6:37 PM Description: With the same settings, under 1.36 login is successful. After upgrade to 1.37, the login timed out and unable to login. Attach the log files (level: all) for both 1.36 and 1.37 version. Environment: Ubuntu 12.04.4 LTS (GNU/Linux 3.8.0-38-generic x86_64) Jenkins ver. 1.532.3 Project: Jenkins Priority: Major Reporter: Rick Liu 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
Alex Lombardi commented on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 Seeing the same issue on both a W2K3 and a W2K8 device. Noticed that a backup instance of the active-directory.jpi named active-directory.bak now exists with the old dat. When i renamed the new jpi smething else and made the backup active all worked well, but the system detected an update was again available which caused the same issue. 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.
