Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42030

BadCredentialsException improperly thrown out of loadUserByUsername

    Details

    • Similar Issues:

      Description

      Attaching log from https://ci.jenkins.io/job/Core/job/jenkins/job/PR-2750/1/consoleText, a failed PR build from Stephen Connolly during a time when R. Tyler Croy was working to restore LDAP service from Jenkins. This build apparently only failed because UserIDCanonicalIdResolver catches declared exceptions but not the BadCredentialsException it actually got.

        Attachments

          Issue Links

            Activity

            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Jesse Glick
            Path:
            src/main/java/hudson/security/LDAPSecurityRealm.java
            http://jenkins-ci.org/commit/ldap-plugin/7000c0915e8aea058f2f951075542217a32734eb
            Log:
            [FIXED JENKINS-42030] If searchForUser fails with BadCredentialsException, wrap in a type we are allowed to throw.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/security/LDAPSecurityRealm.java http://jenkins-ci.org/commit/ldap-plugin/7000c0915e8aea058f2f951075542217a32734eb Log: [FIXED JENKINS-42030] If searchForUser fails with BadCredentialsException, wrap in a type we are allowed to throw.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                jglick Jesse Glick
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: