Repro steps:

1. Create a pipeline job with dynamic trigger being configured. The trigger configuration file is stored locally, so its URL is something like
   "file:///var/lib/jenkins/jobs/some-jenkins-job/lastSuccessful/archive/trigger_config.txt"
2. Push a gerrit code review which is supposed to trigger the pipeline job as its project and branch is specified in the dynamic configuration text file.

Expected outcome:
The pipeline job is triggered to start.

Actual outcome:
The pipeline job is NOT triggered to start.

Workaround:
If the anonymous users is granted the "Overall Read" and "Job Read" rights as shown in the attached picture, the pipeline job is triggered to start as expected.

If you need any other information or logs, please let me know.