Description

The menu (http://myjenkins/configureSecurity) related to Authorize Project Plugin can accept both entries in the same time:

• Project default Build Authorization


• Per-project configurable Build Authorization

But only Project default Build Authorization is applied to all jobs.

Actual Behavior

All jobs, even those with Authorization configured are run with the settings defined for Project default Build Authorization.

Expected Behavior

If a job has an Authorization configured explicitly in its configuration, then this one should be applied. Otherwise, the one defined in for Project default Build Authorization is applied.

Implementation details

This behavior can be discovered in the beginning of the build logs with:

originally caused by:

 Started by user yyy

Running as xxx

---
Originally reported by mhochet, imported from: Configure Global Security should accept both entries: default and per project

• status: Open
  
• priority: Minor
  
• component(s): authorize-project-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20260312-112651
  

Raw content of original issue

Description


The menu (http://myjenkins/configureSecurity) related to Authorize Project Plugin can accept both entries in the same time:



	
Project default Build Authorization

	
Per-project configurable Build Authorization



But only Project default Build Authorization is applied to all jobs.

Actual Behavior


All jobs, even those with Authorization configured are run with the settings defined for Project default Build Authorization.

Expected Behavior


If a job has an Authorization configured explicitly in its configuration, then this one should be applied. Otherwise, the one defined in for Project default Build Authorization is applied.

Implementation details


This behavior can be discovered in the beginning of the build logs with:



originally caused by:

 Started by user yyy

Running as xxx

• environment: All

Start at the Authorize Project Plugin configuration exposed through /configureSecurity and trace how Project default Build Authorization and Per-project configurable Build Authorization are selected for jobs. Use the beginning of the build logs, including the “Started by user” and “Running as” lines, to reproduce the behavior. Done means an explicitly configured job authorization takes precedence, while other jobs use the project default.

Written by the indexing model from the issue text.