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

Active directory user names should not be case sensitive.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • None
    • Windows Server 2008.

      Active directory user names should not be case sensitive. For example if I add the user "paul" then I would expect to be able to also login as "Paul", "pAul" or any other case combination.

      At the moment this won't match any user name and fail to login the user in, or worse match none and apply "authenticated user" permissions. This seems to confuse a lot of users.

      If there is a use case where case sensitivity is required then I think there should be a toggle option to enable or disable it.

          [JENKINS-12607] Active directory user names should not be case sensitive.

          Why is Jenkins passing around usernames and not ultimately referencing some sort of internal numeric user ID?

          This seems like a fundamental architectural issue.

          David Grierson added a comment - Why is Jenkins passing around usernames and not ultimately referencing some sort of internal numeric user ID? This seems like a fundamental architectural issue.

          jothibasu Kamaraj added a comment - - edited

          Any Fix is given for this issue ,we are also facing same issue due to Case Sensitive while trying to apply the Access for the jobs via Role Strategy or Matrix Based security.

          Jenkins Version:1.596.2

          jothibasu Kamaraj added a comment - - edited Any Fix is given for this issue ,we are also facing same issue due to Case Sensitive while trying to apply the Access for the jobs via Role Strategy or Matrix Based security. Jenkins Version:1.596.2

          Mayur Barge added a comment -

          We are also facing this issue.

          Mayur Barge added a comment - We are also facing this issue.

          jothibasu k added a comment -

          Guys any update on this issue... we facing this issue while trying to integrate with JIRA..Please check

          jothibasu k added a comment - Guys any update on this issue... we facing this issue while trying to integrate with JIRA..Please check

          I have this issue too. I find that the user needs to log in to Jenkins with the same case as the user I've created in the role manager. In other words, usernames are not case sensitive when they are passed to Active Directory for confirmation but they are case sensitive once they get back to Jenkins and it tries to use them to give you access. I've bodged it so far by creating lower case and Title Case versions of each user but I'd rather it just worked properly.

          System Administrator added a comment - I have this issue too. I find that the user needs to log in to Jenkins with the same case as the user I've created in the role manager. In other words, usernames are not case sensitive when they are passed to Active Directory for confirmation but they are case sensitive once they get back to Jenkins and it tries to use them to give you access. I've bodged it so far by creating lower case and Title Case versions of each user but I'd rather it just worked properly.

          Thomas Hieber added a comment -

          Same Problem here. The Workaround at the moment: You can enter the user to Jenkins usermanagement with upper or lowercase or any combination of upper and lowercase and it will always be found in Active Directory.
          They will ALWAYS be able to log in and they will always receive the rights given by their groups, but they do only receive individual rights if the name is entered exactly as set in Jenkins user Management.
          So you can tell your users to always use the same combination of upper and lowercase to log in or you can give them rights only based in groups. (which may lead to the need to do administration in LDAP which may or may be not possible for the Jenkins administrators)

          Thomas Hieber added a comment - Same Problem here. The Workaround at the moment: You can enter the user to Jenkins usermanagement with upper or lowercase or any combination of upper and lowercase and it will always be found in Active Directory. They will ALWAYS be able to log in and they will always receive the rights given by their groups, but they do only receive individual rights if the name is entered exactly as set in Jenkins user Management. So you can tell your users to always use the same combination of upper and lowercase to log in or you can give them rights only based in groups. (which may lead to the need to do administration in LDAP which may or may be not possible for the Jenkins administrators)

          M Chon added a comment -

          Switched to using LDAP a while back. (De-installed the Active Directory plugin).
          Very happy with LDAP.

          M Chon added a comment - Switched to using LDAP a while back. (De-installed the Active Directory plugin). Very happy with LDAP.

          Thomas Hieber added a comment -

          We had the described ussues with the LDAP plugin, not with the Active Directory plugin - sorry for the confusion.

          Thomas Hieber added a comment - We had the described ussues with the LDAP plugin, not with the Active Directory plugin - sorry for the confusion.

          Jason Schoon added a comment -

          What would it take to get this under investigation or implemented? This appears to have been an issue for nearly 4 years, and it impacts our organization everytime not just someone new is added, but anytime they forgot to login with the exactly correct case. Not because they get rejected, but because they get in but have the wrong rights. That's a bad combination.

          Jason Schoon added a comment - What would it take to get this under investigation or implemented? This appears to have been an issue for nearly 4 years, and it impacts our organization everytime not just someone new is added, but anytime they forgot to login with the exactly correct case. Not because they get rejected, but because they get in but have the wrong rights. That's a bad combination.

          Oleg Nenashev added a comment -

          jasonschoon Jenkins is an open-source project. If you need this feature, the best way to get progress on it is to propose a pull request to the plugin. Maybe fbelzunc has some plans regarding this change.

          Oleg Nenashev added a comment - jasonschoon Jenkins is an open-source project. If you need this feature, the best way to get progress on it is to propose a pull request to the plugin. Maybe fbelzunc has some plans regarding this change.

            Unassigned Unassigned
            paulm Paul M
            Votes:
            26 Vote for this issue
            Watchers:
            29 Start watching this issue

              Created:
              Updated: