I am struggling with installation of additional P4 trigger for multibranch pipeline job.
We have anonymous user with job build and read permissions granted. so curl without any user and pass onto p4/change works perfectly fine, pipeline jobs are triggered, poked, probed, built.
When it comes to use a curl on the p4/event, for multibranch pipeline job, it throws a 403 No valid crumb was included.
In the Pipeline job description, around Server authentication, one can find that manually providing CRUMB is not needed Deprecated as of 1.8.10 (CRUMB support is embedded). Shouldn't be a case also for p4/event end point?
I am also guessing, when we would try the manual CRUMB obtaining, modern Jenkins would push as to use user/api key flow as well. That's not generally bad to follow up with both triggers to be properly secured, but initially I would like to make them work as-is, unless there is no other way.