Re: No valid crumb - scm trigger doesn't work since 2.222 - pull 4509

2020-03-09 Thread Daniel Beck
> On 9. Mar 2020, at 13:06, Stölzer Sven wrote: > > it seems that since version 2.222 the scm trigger doesn’t work. > The requested Crumb form jenkins server was correctly included in the post > commit hook see attachment. It's unclear to me what happened here. If Jenkins was already

Re: No valid crumb - scm trigger doesn't work since 2.222 - pull 4509

2020-03-09 Thread Slide
Please see this post from the developers group, it mentions the CSRF protections enabled in 2.222 https://groups.google.com/forum/#!topic/jenkinsci-dev/NTlo7lhWY_Q On Mon, Mar 9, 2020 at 5:13 AM Stölzer Sven wrote: > Hi Jenkins-Team, > > > > it seems that since version 2.222 the scm trigger

No valid crumb - scm trigger doesn't work since 2.222 - pull 4509

2020-03-09 Thread Stölzer Sven
Hi Jenkins-Team, it seems that since version 2.222 the scm trigger doesn’t work. The requested Crumb form jenkins server was correctly included in the post commit hook see attachment. But the Jenkins throws an: “HTTP ERROR 403 No valid crumb was included in the request”. Where is the error