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

User-name "is already taken" but not shown in user list

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • _unsorted
    • None

      System tried to send mail to user grixon@ast.cam.ac.uk where grixon is an account that has committed changes to SVN and ast.cam.ac.uk is the default email domain. I went to change that user's email setting and found the account not listed in the "manage users" page. I then tried to create the account and was told "account is already taken".

          [JENKINS-17332] User-name "is already taken" but not shown in user list

          Guy Rixon created issue -

          Stephen Connolly added a comment -

          I don't see how this relates to the credentials plugin.

          The credentials plugin adds screens for managing credentials external to Jenkins, e.g.

          Jenkins » Manage Jenkins » Manage Credentials

          which manages credentials available to all slaves and jobs (i.e. global scope) or all slaves (i.e. system scope)

          and

          People » (the currently logged in user) » Configure

          Which has the option to store credentials for the currently logged in user.

          The second one is only (to my knowledge) really effectively used by the CloudBees Deployer Plugin, but other plugins may start picking it up.

          Stephen Connolly added a comment - I don't see how this relates to the credentials plugin. The credentials plugin adds screens for managing credentials external to Jenkins, e.g. Jenkins » Manage Jenkins » Manage Credentials which manages credentials available to all slaves and jobs (i.e. global scope) or all slaves (i.e. system scope) and People » (the currently logged in user) » Configure Which has the option to store credentials for the currently logged in user. The second one is only (to my knowledge) really effectively used by the CloudBees Deployer Plugin, but other plugins may start picking it up.

          Stephen Connolly added a comment -

          If re-opening, please select the correct component or justify why this is against the credentials plugin

          Stephen Connolly added a comment - If re-opening, please select the correct component or justify why this is against the credentials plugin
          Stephen Connolly made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Kanstantsin Shautsou added a comment -

          This comes from core, username is taken by SCM people, that's why a real user can't create account with the same username.

          Kanstantsin Shautsou added a comment - This comes from core, username is taken by SCM people, that's why a real user can't create account with the same username.
          Kanstantsin Shautsou made changes -
          Component/s New: security [ 15508 ]
          Component/s Original: credentials [ 16523 ]
          Affects Version/s Original: current [ 10162 ]
          Assignee Original: Stephen Connolly [ stephenconnolly ]
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Kanstantsin Shautsou made changes -
          Resolution Original: Cannot Reproduce [ 5 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          Kanstantsin Shautsou added a comment - - edited

          This thing is very odd.
          If you configured jenkins with:
          "Security realm" -> "own database" + "allow sign up"
          Then after runing some build that creates SCM people, you can't "sign up" with existed SCM username.
          Probably during sign up jenkins should check user database instead of SCM people.
          https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java#L311

          This problem can be bypassed by setting password in /user/USERNAME/configure manually by administrator. It will automatically create real internal user /securityRealm/

          Kanstantsin Shautsou added a comment - - edited This thing is very odd. If you configured jenkins with: "Security realm" -> "own database" + "allow sign up" Then after runing some build that creates SCM people, you can't "sign up" with existed SCM username. Probably during sign up jenkins should check user database instead of SCM people. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java#L311 This problem can be bypassed by setting password in /user/USERNAME/configure manually by administrator. It will automatically create real internal user /securityRealm/
          Kanstantsin Shautsou made changes -
          Assignee New: Kanstantsin Shautsou [ integer ]
          Kanstantsin Shautsou made changes -
          Status Original: Reopened [ 4 ] New: In Progress [ 3 ]

            mc1arke Michael Clarke
            guyrixon Guy Rixon
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: