[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title CJ Harmath commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them This is how my job's config.xml starts '1.1' encoding='UTF-8'?> "workflow-multibranch@2.21"> test rest.impl.pipeline.credential.BlueOceanCredentialsProvider_-FolderPropertyImpl plugin="blueocean-pipeline-scm-api@1.14.0"> "credentials@2.1.19"> blueocean-folder-credential-domain Blue Ocean Folder Credentials domain testuser github-enterprise:bd08318e10264d38792523a9e76b6f818f8ec73616f7b13b99692ed940ce642c rest.impl.pipeline.credential.BlueOceanCredentialsProvider_-FolderPropertyImpl> "pipeline-model-definition@1.3.8"> "docker-commons@1.14"/> And I wonder if the BlueOceanCredentialProvider which references the testuser's credential can be changed to use the global credential instead. I already have a jenkins level github enterprise access token credential, so i would like to just use that. That token btw was issued to a service account which is also added on the GitHub Enterprise side with a nice Jenkins icon, so it looks much better than the pipeline creator's photo next to a Pull request check. I've just changed the testuser to jenkins user then updated the user level credential as well and it works, but it's hacky and too involved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title CJ Harmath commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them I've stumbled up this as I was curious how to setup a pipeline with a global credential instead of a user specific. Currently when a user creates a new pipeline at first time, he/she will be asked for a personal access token for github which then gets stored in the users credential. Since users can come and go, it would be more practical if an administrator can set the credential. This also has an added value of GitHub checks not showing the user who created the pipeline, but the user configured by the admin. Happy to submit a new issue. Thanks, CJ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193214.1534948736000.23134.1559875380213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title William Laszlo commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them Sure, thank you! Even if I make the update, I don't know when this would happen again to my team (when someone is deleted from LDAP). I really can't test it when I want. I hope that no-one will have this issue from now. I recreated the job when I figured out that I found a bug and I was able to run it. I can't confirm now that it's ok or not because I don't have anymore that original job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them William Laszlo this was released on friday, so let me know if you continue to have problems once you upgrade (if you upgrade) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan updated JENKINS-53188 Jenkins / JENKINS-53188 New jobs created from Blue Ocean are tied with username that created them Change By: Gavin Mogan Status: Fixed but Unreleased Resolved Released As: 1.13.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan updated JENKINS-53188 Jenkins / JENKINS-53188 New jobs created from Blue Ocean are tied with username that created them Change By: Gavin Mogan Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them https://github.com/jenkinsci/blueocean-plugin/pull/1915 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title William Laszlo edited a comment on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them I don't know how they were users are deleted from LDAP. I can confirm that it's still existing in $JENKINS_HOME/users/users.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title William Laszlo commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them I don't know how they were deleted from LDAP. I can confirm that it's still existing in $JENKINS_HOME/users/users.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them (I can catch it, its UsernameNotFoundException, so fixable, but want to know if ldap needs a patch to clean up properly) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them Note, I was able to reproduce this by deleting the folder users/deleteme_729664863048313 but the user was still in users.xml When i delete the user within the UI, it actually errors out properly. Looks like there's a map inside of $JENKINS_HOME/users/users.xml that maps usernames to the files on the disk. William Laszlo: from the stacktrace, it looks like ldap is being used. Do you know how the user was actually deleted? Are they still inside users.xml? is the file still on the disk? (I'll see if there's a way to find out if you don't have disk access) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them Okay, I was able to reproduce it with latest master (1.11.1) and jenkins (2.150.2) so not version dependant. Looks like when you create a new pipeline with blueocean, it attaches the credentials to that project's folder Then it tries to impersonate and grab that credential to be used https://github.com/jenkinsci/blueocean-plugin/blob/1944c62bc252253450e15b5eaddd359963118a8b/blueocean-pipeline-scm-api/src/main/java/io/jenkins/blueocean/rest/impl/pipeline/credential/BlueOceanCredentialsProvider.java#L76 Now that I tracked it down, i'll add a test and try to get it fixed up. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title William Laszlo commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them Jenkins 2.121.1 Blue Ocean 1.9.0 I'm pretty sure that he (user cadana) created the credentials for SCM which were used. SCM credentials are not tied with his account because everything else was working. On run I've got the message from description and on settings view what is in screenshot. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them I haven't been able to reproduce this, but I have one more thing to try. What version of blue ocean are you using? what version of jenkins? Could credentials have been tied to that user? Does it happen on run? on view? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-53188 New jobs created from Blue Ocean are tied with username that created them Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title
William Laszlo updated an issue
Jenkins / JENKINS-53188
New jobs created from Blue Ocean are tied with username that created them
Change By:
William Laszlo
An A colleague (let's say, username cadana) created a Multibranch Pipeline job from Blue Ocean, with Github SCM (username for SCM is not tied in any way with cadana) and now he left the company. I had to copy the job manually to "recreate" it, to lose the first owner that no longer exists to fix this error.A build log from a job:{noformat}Started by user Laszlo, William Daniel[BFA] Scanning build for known causes...[BFA] No failure causes found[BFA] Done. 0sorg.acegisecurity.userdetails.UsernameNotFoundException: User cadana not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1314) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1251) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.getUserDetailsForImpersonation(User.java:349) at hudson.model.User.impersonate(User.java:329) at io.jenkins.blueocean.rest.impl.pipeline.credential.BlueOceanCredentialsProvider.getCredentials(BlueOceanCredentialsProvider.java:76) at com.cloudbees.plugins.credentials.CredentialsProvider.lookupCredentials(CredentialsProvider.java:413) at com.cloudbees.plugins.credentials.CredentialsProvider.lookupCredentials(CredentialsProvider.java:532) at org.jenkinsci.plugins.github_branch_source.Connector.lookupScanCredentials(Connector.java:234) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1399) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:566) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}
Add Comment
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title
William Laszlo updated an issue
Jenkins / JENKINS-53188
New jobs created from Blue Ocean are tied with username that created them
Change By:
William Laszlo
An colleague (let's say, username cadana) created a Multibranch Pipeline job from Blue Ocean, with Github SCM (username for SCM is not tied in any way with cadana) and now he left the company. I had to copy the job manually to "recreate" it, to lose the first owner that no longer exists to fix this error. A build log from a job: {noformat}Started by user Laszlo, William Daniel[BFA] Scanning build for known causes...[BFA] No failure causes found[BFA] Done. 0sorg.acegisecurity.userdetails.UsernameNotFoundException: User cadana not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1314) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1251) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.getUserDetailsForImpersonation(User.java:349) at hudson.model.User.impersonate(User.java:329) at io.jenkins.blueocean.rest.impl.pipeline.credential.BlueOceanCredentialsProvider.getCredentials(BlueOceanCredentialsProvider.java:76) at com.cloudbees.plugins.credentials.CredentialsProvider.lookupCredentials(CredentialsProvider.java:413) at com.cloudbees.plugins.credentials.CredentialsProvider.lookupCredentials(CredentialsProvider.java:532) at org.jenkinsci.plugins.github_branch_source.Connector.lookupScanCredentials(Connector.java:234) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1399) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:566) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}
Add Comment
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title William Laszlo created an issue Jenkins / JENKINS-53188 New jobs created from Blue Ocean are tied with username that created them Issue Type: Bug Assignee: Unassigned Attachments: usernameNotFound.png Components: blueocean-plugin Created: 2018-08-22 14:38 Priority: Minor Reporter: William Laszlo An colleague (let's say, username cadana) created a Multibranch Pipeline job from Blue Ocean, with Github SCM (username for SCM is not tied in any way with cadana) and now he left the company. I had to copy the job manually to "recreate" it, to lose the first owner that no longer exists to fix this error. Started by user Laszlo, William Daniel [BFA] Scanning build for known causes... [BFA] No failure causes found [BFA] Done. 0s org.acegisecurity.userdetails.UsernameNotFoundException: User cadana not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1314) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1251) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.getUserDetailsForImpersonation(User.java:349) at hudson.model.User.impersonate(User.java:329) at io.jenkins.blueocean.rest.impl.pipeline.credential.BlueOceanCredentialsProvider.getCredentials(BlueOceanCredentialsProvider.java:76) at
