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

SVN user name takes over Hudson's one and all Hudson't permissions are lost

    Details

    • Similar Issues:

      Description

      I'm a Hudson administrator with all permissions possible and my username in Hudson is "evgeny".
      Starting with 1.341 I've noticed my username displayed (top right corner) by Hudson is "Evgeny" and I have no permissions to administer Hudson any more or even configure a job, much like anonymous access (anonymous users are only allowed to see and run the jobs). Back to 1.339 - "evgeny" + all permissions are back. Now switch to 1.342 and create "evgeny" again - it works but after couple of days "Evgeny" takes over and all permissions are lost again

      Someone figured out it may have something to do with SVN users - we don't have any kind of mapping from SVN users making commits to Hudson users. In fact, with 30+ SVN users we only have 2-3 Hudson users for administrators and all other people in organization are using Hudson anonymously (like I said, they can only see and run a job, no more than that)

      And my SVN user is "evgeny" as well - that could explain this strange behavior.
      I've now changed my Hudson user to "evgenyg", to make it different from SVN user "evgeny". And it seems working.

      Thank you!

        Attachments

          Issue Links

            Activity

            Hide
            mdonohue mdonohue added a comment -

            This is probably a side effect of JENKINS-4354, which was fixed in release 1.340. I doubt subversion has anything to do with it. You probably had two users previously "evgeny" and "Evgeny" and the bug fix only allows you to access "Evgeny" I would look at hudson's configuration files to delete your doppelganger account.

            Show
            mdonohue mdonohue added a comment - This is probably a side effect of JENKINS-4354 , which was fixed in release 1.340. I doubt subversion has anything to do with it. You probably had two users previously "evgeny" and "Evgeny" and the bug fix only allows you to access "Evgeny" I would look at hudson's configuration files to delete your doppelganger account.
            Hide
            evgeny_goldin evgeny_goldin added a comment -

            No, there was no previous user "Evgeny" as I'm the one creating all of them
            It's SVN users kind of "becoming" Hudson users as well and I believe it was my SVN user taking over my Hudson user.

            The issue pointed out says "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" - but that seems to be our case. All SVN users are brought to Hudson as "User" (first letter uppercased) and sometimes people (me!) create a separate Hudson user as "user". That's where we had "Evgeny" and "evgeny".

            Show
            evgeny_goldin evgeny_goldin added a comment - No, there was no previous user "Evgeny" as I'm the one creating all of them It's SVN users kind of "becoming" Hudson users as well and I believe it was my SVN user taking over my Hudson user. The issue pointed out says "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" - but that seems to be our case. All SVN users are brought to Hudson as "User" (first letter uppercased) and sometimes people (me!) create a separate Hudson user as "user". That's where we had "Evgeny" and "evgeny".
            Hide
            jamesdumay James Dumay added a comment -

            There have been numerous fixes and upgrades to the Subversion plugin in the intervening years between this ticket being filed and today. If this is still a problem with the latest version of Jenkins and the subversion plugin, please open a new ticket with detailed reproduction instructions and we can take a look.

            Show
            jamesdumay James Dumay added a comment - There have been numerous fixes and upgrades to the Subversion plugin in the intervening years between this ticket being filed and today. If this is still a problem with the latest version of Jenkins and the subversion plugin, please open a new ticket with detailed reproduction instructions and we can take a look.

              People

              • Assignee:
                Unassigned
                Reporter:
                evgeny_goldin evgeny_goldin
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: