[JIRA] (JENKINS-13788) Git user and Crowd 2 authenticated user should be equal (one User-Id)
micheljung commented on JENKINS-13788 Git user and Crowd 2 authenticated user should be equal (one User-Id) Same with Crowd Plugin 1.5, Jenkins 1.493 and Subversion Plugin 1.43 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13788) Git user and Crowd 2 authenticated user should be equal (one User-Id)
Thomas Lehmann commented on JENKINS-13788 Git user and Crowd 2 authenticated user should be equal (one User-Id) Sorry, what do you mean with "the user generated out of the Git user"? Regardless of whether using the Crowd plugin or not, the Git plugin (or Jenkins) create users (in Filesystem) out of the users found in the Git history. I can see this because there were Git-identities named "logonname logonn...@somedevelopershost.acme.com" when a user forgot to set its identity in the Git config. Now you've lost me... How do you "generate" users/usernames? Let's not say users/usernames are generated but "persons". One users will appear multiple (at least two) times in the Persons page (this is what I've called users before). One user is reflected by the Crowd user, another by the developers git identity. My guess is that the problem is in the Crowd plugin and not in the Git plugin. I don't think this is related to the Git nor the Crowd plugin but Jenkins. Because there are multiple authentication and versioning plugins they shouldn't care about each other to solve this issue. Jenkins should provide a mechanism to associate a VCS identity with Jenkins identity (optionally provided by an authentication plugin). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13788) Git user and Crowd 2 authenticated user should be equal (one User-Id)
Thomas Lehmann edited a comment on JENKINS-13788 Git user and Crowd 2 authenticated user should be equal (one User-Id) Sorry, what do you mean with "the user generated out of the Git user"? Regardless of whether using the Crowd plugin or not, the Git plugin (or Jenkins) create users (in Filesystem) out of the users found in the Git history. I can see this because there were Git-identities named "logonname logonn...@somedevelopershost.acme.com" when a user forgot to set its identity in the Git config. Now you've lost me... How do you "generate" users/usernames? Let's not say users/usernames are generated but "persons". One users will appear multiple (at least two) times in the Persons page (this is what I've called users before). One userperson is reflected by the Crowd user, another by the developers Git identity. My guess is that the problem is in the Crowd plugin and not in the Git plugin. I don't think this is related to the Git nor the Crowd plugin but Jenkins. Because there are multiple authentication and versioning plugins they shouldn't care about each other to solve this issue. Jenkins should provide a mechanism to associate a VCS identity with Jenkins identity (optionally provided by an authentication plugin). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13788) Git user and Crowd 2 authenticated user should be equal (one User-Id)
bloomper commented on JENKINS-13788 Git user and Crowd 2 authenticated user should be equal (one User-Id) Hi! I think I have run into the same problem as the creator of this issue. We have a setup with Stash/Git, Crowd and Jenkins. When logging into Jenkins, Jenkins checks the credentials with Crowd and if it is a new user, Jenkins creates a user. When doing so, it uses the full name + username from Crowd, e.g. 'Anders Jacobsson (netjaan)', as the user id. However, this is obviously not the same as what is configured for git, i.e. user.name = netjaan. This results in Jenkins not being able to match commits with already existing users (there is another bug, JENKINS-14250, that is also related to this). My guess is that the problem is in the Crowd plugin and not in the Git plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13788) Git user and Crowd 2 authenticated user should be equal (one User-Id)
Thomas Lehmann created JENKINS-13788: Summary: Git user and Crowd 2 authenticated user should be equal (one User-Id) Key: JENKINS-13788 URL: https://issues.jenkins-ci.org/browse/JENKINS-13788 Project: Jenkins Issue Type: Bug Components: crowd2, git Affects Versions: current Environment: Jenkins 1.462 on CentOS 5.8 SunJDK 1.7.0_03-b04 Crowd2 Plugin 1.4 Git Plugin 1.1.12 Against Crowd 2.4.2 Reporter: Thomas Lehmann Assignee: Thorsten Heit This is very complicated to describe. I'll try to describe our setup, our Jenkins configuration's chronology the problem and my assumptions to the current bug... I'll describe the whole situation which probably makes the description harder to understand, but I want to provide as much information as possible. Please help me to make this description more specifcally and/or create another issue for separate problems. Thank you. :) Setup -- Jenkins configured to authenticate through Crowd 2 Plugin (works fine so far, also with authorization) The authenticated username is Forename Lastname (crowd-userid). Crowd holds the crentral email address of each user. Out projects are checked out through Git. Older commits may have malformed auther name and email. Recent commits are all in form Username = 'Forename Lastname' and email = 'The same email address as in crowd'. Cronology -- - This Jenkins installation started with no security configured. - I can't ensure there was never a Jenkins-based usermanagement configured as this installation was administered by a colleague before. - All jobs check out from a Git-Repository - Before today the Peoples view showed a variety of user id from more or less real names (also misleading names like root, see my assumptions below) over through odd usernames like contextMenu (we can't figure out what caused this username). - Some users seemed to appear twice (this is actually another issue) - Today I've configures authentication through the Crowd 2 Plugin - Now there are further users, one for each Crowd user that has logged in once Problem There are at least 2, sometimes 3 users (obviously depending on how much different Git users exists) in Peoples view. Only one of them, apparently the user generated out of the Git user can show information under Builds Assumptions - A username is generated for each user of a Git commit - If there was accidently no username like or login login@hostname or root root@hostname such user IDs (, login, root) will be generated So how can I... - delete these accidently created users - tell Jenkins to see/understand automatically generated user x is equal to Crowd user X or at least map each Git user to a Crow 2 user - keep Jenkins from generating user IDs for all Git users I know there are other issues and solutions on the web about removing users, but deleting in users/ did not work either. All user-directories are re-generated on Jenkins startup (all having statup date). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
