How to access Jenkins APIs after anonymous read was disabled

Summary

The latest Eclipse I-build failed with

+ curl --fail https://ci.eclipse.org/releng/job/Builds/job/I-build-4.40/94//wfapi/describe
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 403

See https://ci.eclipse.org/releng/job/Builds/job/I-build-4.40/94/console
and https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/3804

This failure seems permanent, verified it wit another job, and I assume this is a consequence of

• https://github.com/eclipse-cbi/jiro/commit/5fa6391daeabb29b0c272b69c64586ec85bf5c36

Could you advice us how to resolve this? Do we need a special token for non-anonymous access or could the access configuration be refined to allow read access to a job from within that same job (or maybe even from the same Jenkins instance)?

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

We can't produce integration builds of the Eclipse TLP any more.