• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: Other, OS: All

      As of now the names of users (id) are case sensitive. Retrieving user "name" and
      "Name" returns different User objects. Each user data is then stored in separete
      folders; "users/name/" and "users/Name". This is fine on linux as files are case
      sensitive, but not so good on Windows as file names are case insensitive.

      On Windows the user "Name" and "name", will be different users but after a
      server restart they will be populated with the same data. It is the same data as
      both user objects has been loaded with data from the "users/name" folder. So
      this means that on Windows, the user objects should be the same as they contain
      the same data.

      The background to this enhancement is that I have two issues reported on the ci-
      game (3990 and 4350). Depending on how people log in to a machine, they will
      have different casing on their user name. This is fine, but the big problem (in
      my eyes) is that Hudson stores two different user's data in one folder. Therefore I think Hudson should treat user names case insensitive, as the users
      is the same person (ie same data after a restart).

      The effect of this change would be small as I dont think there are no hudson
      installations that have users with different casing in their names and still
      would like to make a distinction between them.

          [JENKINS-4354] Make Hudson user names case insensitive

          redsolo created issue -

          Taciano Tres added a comment -

          This is an issue to me too, since our users are authenticated on LDAP
          (configured as case insensitive), and some users uses uppercase and some uses
          lowercase login UID. In either case Hudson should obey the case returned by
          LDAP.

          Taciano Tres added a comment - This is an issue to me too, since our users are authenticated on LDAP (configured as case insensitive), and some users uses uppercase and some uses lowercase login UID. In either case Hudson should obey the case returned by LDAP.

          mdonohue added a comment -
              • Issue 4550 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 4550 has been marked as a duplicate of this issue. ***
          mdonohue made changes -
          Link New: This issue is duplicated by JENKINS-4550 [ JENKINS-4550 ]

          Code changed in hudson
          User: : kohsuke
          Path:
          trunk/hudson/main/core/src/main/java/hudson/model/User.java
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=24879
          Log:
          [FIXED JENKINS-4354] in 1.340. User IDs are now case preserving but case insensitive

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : kohsuke Path: trunk/hudson/main/core/src/main/java/hudson/model/User.java trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=24879 Log: [FIXED JENKINS-4354] in 1.340. User IDs are now case preserving but case insensitive
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          mdonohue made changes -
          Link New: This issue is blocking JENKINS-5436 [ JENKINS-5436 ]

          Taciano Tres added a comment -

          Sorry about being late, but just today have some time to test the fix.
          But it don't work, at least not completely. The issue that remains is that the permissions should be case insensitive too: if the user 'bob' has the permission, the authenticated user 'Bob' should have it too.
          I can authenticate the users case insensitively, but can't authorize it.
          Mu vote is for reopen this bug.

          Taciano Tres added a comment - Sorry about being late, but just today have some time to test the fix. But it don't work, at least not completely. The issue that remains is that the permissions should be case insensitive too: if the user 'bob' has the permission, the authenticated user 'Bob' should have it too. I can authenticate the users case insensitively, but can't authorize it. Mu vote is for reopen this bug.

          Taciano Tres added a comment -

          Anyone against reopening this issue?
          Doing in 3 ... 2 ... 1 ...

          Taciano Tres added a comment - Anyone against reopening this issue? Doing in 3 ... 2 ... 1 ...
          Taciano Tres made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

            Unassigned Unassigned
            redsolo redsolo
            Votes:
            17 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated:
              Resolved: