> On 9. Mar 2020, at 13:06, Stölzer Sven <sstoel...@baumer.com> 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 configured to require CSRF crumbs before the update,
then nothing should have changed.
If that wasn't the case however, but the script already submitted CSRF crumbs,
those should have been unnecessary in the past…? So why did it do that? Who or
what generated that command?
If you recently adapted your script to submit CSRF crumbs after the update, you
didn't do it quite right. Why, and how to solve it, is explained at
https://jenkins.io/doc/upgrade-guide/2.176/#SECURITY-626
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/64A3271B-9DB6-40E8-ABAD-48FFE689B5E5%40beckweb.net.
