[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships

[alexhra...@gmail.com (JIRA)]

Title: Message Title

Alex Raber edited a comment on JENKINS-59105   Re: Accessing Jenkins using API token does not work in group memberships More details:   I added this to JENKINS_OPS in my jenkins.sh (I'm running in k8s via docker): {{jenkins_opts_array=('-Dhudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO=true')}} ^ per: [https://jenkins.io/doc/upgrade-guide/2.204/#upgrading-to-jenkins-lts-2-204-6] I then generated a new token for my user, and set up my Github repo webhook as follows: url: [https://dev-jenkins.url.gov/job/testjob/build] secret: <user-token> (with admin/owner perms) application/json Then click apply and then click the test button from github. 403. I have also enabled and disabled the Enable proxy compatibility CSRF checkbox in Global Security. Note my testing is done in a sandbox, but the issue is impacting my production jenkins as well. I'd prefer not to roll back if possible. Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.201528.1566922172000.7799.1586286600419%40Atlassian.JIRA.