[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors

2019-06-12 Thread ke...@rkn.la (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Nelson edited a comment on  JENKINS-57595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors   
 

  
 
 
 
 

 
 To clarify our symptoms a bit:We're using  Jenkins 2.176.1 (LTS),  the GitHub  OAuth  Authentication 0.32  plugin with a GitHub Enterprise install , and Matrix Authorization Strategy Plugin 2 . 4.2.   I'm able to configure the GitHub integration successfully, and use "Logged-in users can do anything" without issue.  I can save this, reload the page and everything works fine.When I select the Matrix-based security radio, I am able to add exactly one user, and set all permissions, and save successfully.  When I try to add more than one user, or when I try to add subsequent users after the first one, I am hit with the "No valid crumb was included in the request" error.  
 

  
 
 
 
 

 
 
 

 
 
 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.199519.1558510674000.25875.1560334740350%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors

2019-06-12 Thread ke...@rkn.la (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Nelson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57595  
 
 
  with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors   
 

  
 
 
 
 

 
Change By: 
 Kevin Nelson  
 
 
Component/s: 
 matrix-auth-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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.199519.1558510674000.25868.1560334560427%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors

2019-06-12 Thread ke...@rkn.la (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Nelson commented on  JENKINS-57595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors   
 

  
 
 
 
 

 
 To clarify our symptoms a bit: We're using the GitHub OAuth plugin with a GitHub Enterprise install.  I'm able to configure the GitHub integration successfully, and use "Logged-in users can do anything" without issue.  I can save this, reload the page and everything works fine. When I select the Matrix-based security radio, I am able to add exactly one user, and set all permissions, and save successfully.  When I try to add more than one user, or when I try to add subsequent users after the first one, I am hit with the "No valid crumb was included in the request" error.  
 

  
 
 
 
 

 
 
 

 
 
 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.199519.1558510674000.25859.1560334380529%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors

2019-06-12 Thread ke...@rkn.la (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Nelson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57595  
 
 
  with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors   
 

  
 
 
 
 

 
Change By: 
 Kevin Nelson  
 
 
Priority: 
 Minor Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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.199519.1558510674000.25852.1560334140973%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors

2019-06-12 Thread ke...@rkn.la (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Nelson commented on  JENKINS-57595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors   
 

  
 
 
 
 

 
 This is happening on my install as well.  I'm raising the priority to Blocker, since it is currently impacting our organization's ability to use Jenkins at all.  
 

  
 
 
 
 

 
 
 

 
 
 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.199519.1558510674000.25845.1560334140807%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-27332) git-plugin no longer detects changes of branch with /

2017-03-01 Thread ke...@rkn.la (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Nelson commented on  JENKINS-27332  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-plugin no longer detects changes of branch with /   
 

  
 
 
 
 

 
 Mark Waite I'm not 100% sure where the issue is, but here is roughly what I have set up: 1. Existing setup running Jenkins 2.32.1, Git Client 2.3.0, Git Plugin 3.0.5, GitHub Plugin 1.26.1, GitHub Branch Source Plugin 2.0.3, and a bunch of other, seemingly unrelated plugins installed (apologies that this isn't a minimal setup to reproduce – I don't have enough existing knowledge of setting up Jenkins for that to be a simple task) 2. Create "New Item" with a GitHub Organization project type 3. Set up the repository sources (private GitHub organization, proper credentials).. Despite what the instructions [here](https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin) say, there is no checkbox for "Build when a change is pushed to GitHub" 4. After Saving the repository source, the organization scans, and the relevant repository also scans. During the scan, branches with a slash in them are picked up just fine. Everything gets triggered the first time. 5. Create a new branch in the repo with a slash (for example, `feature/testing-slashes`), make a whitespace change somewhere, and push a commit 6. Observe that this very first push does trigger a test properly. 7. Make another whitespace change to the new branch, and commit and push that change 8. The branch update does not trigger a test. I can see in the "All logs" that the GitHub webhook is arriving to Jenkins correctly for the update push, but I don't see any indication in the logs of what happens after the webhook is received. Another thing that I've observed is that if I navigate to the specific repository and then click on "Scan Repository", then click on "Events", I can see a "CREATED" event in response to the original push of the `feature/test-branch`, which successfully triggers the build, but there is no indication of the UPDATED event for the second push. When I update another branch that doesn't have a slash in it, I do see an UPDATED event that does successfully trigger a build. Hopefully this helps some. Let me know if there's any other info that I can provide (and preferably how to collect the info, since I'm still fairly new to Jenkins). Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
 

[JIRA] (JENKINS-27332) git-plugin no longer detects changes of branch with /

2017-02-28 Thread ke...@rkn.la (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Nelson commented on  JENKINS-27332  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-plugin no longer detects changes of branch with /   
 

  
 
 
 
 

 
 I'm experiencing similar symptoms to the original post of this issue, leading me to think that the issue is still here in version 3.0.5. Particularly: Pushing a new branch named `foo/whatever` triggers correctly, but any subsequent pushes to the same branch do not get picked up and triggered. Branches that don't have slashes in them appear to behave just fine.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.