[JIRA] (JENKINS-13025) Active Directory Plugin version 1.26 results in org.acegisecurity.BadCredentialsException: Failed to retrieve user information when 1.24 does not
[ https://issues.jenkins-ci.org/browse/JENKINS-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi resolved JENKINS-13025. - Assignee: Kohsuke Kawaguchi Resolution: Fixed Active Directory Plugin version 1.26 results in org.acegisecurity.BadCredentialsException: Failed to retrieve user information when 1.24 does not --- Key: JENKINS-13025 URL: https://issues.jenkins-ci.org/browse/JENKINS-13025 Project: Jenkins Issue Type: Bug Components: active-directory Environment: jenkins-1.424.6-1.1.noarch RPM on x86_64 CentOS 6.2, active directory plugin 1.24 versus 1.26 Reporter: Don Lindsay Assignee: Kohsuke Kawaguchi All of our login IDs are LDAP/Active Directory names. We can log in. When we upgraded the Active Directory plugin to 1.26, we noticed that the Configure System contained error indications. Specifically, under Authorization, there is a user/group list, and each username had been replaced by an error indication. Examination showed the same error for each username. For example: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for d_lindsay; nested exception is javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece\ufffd]; remaining name 'DC=ocarina,DC=local' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProv\ ider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231) Reverting to the 1.24 plugin fixed this. -- 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
[JIRA] (JENKINS-13025) Active Directory Plugin version 1.26 results in org.acegisecurity.BadCredentialsException: Failed to retrieve user information when 1.24 does not
[ https://issues.jenkins-ci.org/browse/JENKINS-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160325#comment-160325 ] Troels Madsen commented on JENKINS-13025: - I'm also observing this issue using Jenkins 1.454 and active directory plugin 1.26 Active Directory Plugin version 1.26 results in org.acegisecurity.BadCredentialsException: Failed to retrieve user information when 1.24 does not --- Key: JENKINS-13025 URL: https://issues.jenkins-ci.org/browse/JENKINS-13025 Project: Jenkins Issue Type: Bug Components: active-directory Environment: jenkins-1.424.6-1.1.noarch RPM on x86_64 CentOS 6.2, active directory plugin 1.24 versus 1.26 Reporter: Don Lindsay All of our login IDs are LDAP/Active Directory names. We can log in. When we upgraded the Active Directory plugin to 1.26, we noticed that the Configure System contained error indications. Specifically, under Authorization, there is a user/group list, and each username had been replaced by an error indication. Examination showed the same error for each username. For example: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for d_lindsay; nested exception is javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece\ufffd]; remaining name 'DC=ocarina,DC=local' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProv\ ider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231) Reverting to the 1.24 plugin fixed this. -- 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
[JIRA] (JENKINS-13025) Active Directory Plugin version 1.26 results in org.acegisecurity.BadCredentialsException: Failed to retrieve user information when 1.24 does not
Don Lindsay created JENKINS-13025: - Summary: Active Directory Plugin version 1.26 results in org.acegisecurity.BadCredentialsException: Failed to retrieve user information when 1.24 does not Key: JENKINS-13025 URL: https://issues.jenkins-ci.org/browse/JENKINS-13025 Project: Jenkins Issue Type: Bug Components: active-directory Environment: jenkins-1.424.6-1.1.noarch RPM on x86_64 CentOS 6.2, active directory plugin 1.24 versus 1.26 Reporter: Don Lindsay All of our login IDs are LDAP/Active Directory names. We can log in. When we upgraded the Active Directory plugin to 1.26, we noticed that the Configure System contained error indications. Specifically, under Authorization, there is a user/group list, and each username had been replaced by an error indication. Examination showed the same error for each username. For example: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for d_lindsay; nested exception is javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece\ufffd]; remaining name 'DC=ocarina,DC=local' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProv\ ider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231) Reverting to the 1.24 plugin fixed this. -- 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
