[JIRA] (JENKINS-61803) Configure Global Security should accept both entries: default and per project

[maxime.hochet@gmail.com (JIRA)]

Maxime Hochet created an issue

Jenkins / JENKINS-61803 Configure Global Security should accept both entries: default and per project Issue Type: Bug Assignee: Unassigned Components: authorize-project-plugin Created: 2020-04-03 13:20 Environment: All Priority: Minor Reporter: Maxime Hochet Description The menu (http://myjenkins/configureSecurity) related to Authorize Project Plugin can accept both entries: 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 Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[maxime.hochet@gmail.com (JIRA)]

Maxime Hochet updated an issue

Jenkins / JENKINS-61803 Configure Global Security should accept both entries: default and per project

Change By: Maxime Hochet h1. 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.

h1. Actual Behavior

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

h1. 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.

h1. Implementation details

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

{code :java }

originally caused by: Started by user yyy Running as xxx

{code}

Add Comment

[mail@ron.gebauers.org (JIRA)]

Ron Gebauer commented on JENKINS-61803

Re: Configure Global Security should accept both entries: default and per project Maxime Hochet the order is also important. You need to set the per project base before default … because otherwise always default is used. I also do not understand why I can prioritize 2 options … but it seems this is is the case.

Add Comment