From 207d6f06a6539e5d7e2a0457d5b509452e3f18ea Mon Sep 17 00:00:00 2001
From: Michal Konečný <mkonecny@redhat.com>
Date: Nov 29 2022 13:45:05 +0000
Subject: Add Global security step to Jenkins CI configuration


When migrating to new instance I encountered issue getting 403 when triggering
jobs from pagure. Documenting the solution in pagure documentation.

Signed-off-by: Michal Konečný <mkonecny@redhat.com>

---

diff --git a/doc/usage/pagure_ci_jenkins.rst b/doc/usage/pagure_ci_jenkins.rst
index 629b1b7..fef429b 100644
--- a/doc/usage/pagure_ci_jenkins.rst
+++ b/doc/usage/pagure_ci_jenkins.rst
@@ -146,3 +146,7 @@ Example function used in Jenkins pipeline script
            sh "timeout 1 curl -X POST -d \'$json\' https://pagure.io/api/0/ci/jenkins/$repo/\${PAGURE_PUSH_SECRET}/build-finished -H \"Content-Type: application/json\" | true"
        }
    }
+
+* To be able to trigger builds from Pagure CI you need to change the Global Security. Go
+  to `Manage Jenkins` -> `Configure Global Security` and find `Authorization` section.
+  In `Matrix-based security` add Read permission to `Anonymous Users` for Overall/Job/View.