Support global default authorization strategy in Authorize Project

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Due to security reasons, sometimes Jenkins admins may want to completely restrict running jobs as a system/anonymous and setup custom security limitations. In such case it would be useful to add the following features:

      • Global default strategy (if no one configured at the project level)
      • Enforced global strategy, which prevents setting other strategies on the project level

            Assignee:
            ikedam
            Reporter:
            Oleg Nenashev
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: