-
Improvement
-
Resolution: Fixed
-
Major
-
None
Copyartifact performs permission checks only when projects to copy from are specified with variables: See https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact
This is misleading, users are often confused and that results in many JIRA issues.
As the latest Jenkins provides a more flexible authorization model (QueueItemAuthenticator), it's time for copyartifact to check permissions even for projects specified without variables.
- is related to
-
JENKINS-22460 Support artifacts permission
-
- Closed
-
-
JENKINS-23475 Can bypass permission check of CopyArtifact with WebAPI/CLI
-
- Closed
-
-
JENKINS-28247 Can bypass permission check of CopyArtifact with WorkflowJob
-
- Closed
-
-
JENKINS-24892 Copyartifact 2.0
-
- Closed
-
[JENKINS-24888] Complete runtime permission check of Copyartifact
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 158416 ] | New: JNJira + In-Review [ 179740 ] |
Link | New: This issue relates to SECURITY-988 [ SECURITY-988 ] |
Released As | New: https://github.com/jenkinsci/copyartifact-plugin/blob/master/CHANGELOG.adoc#144 | |
Assignee | New: ikedam [ ikedam ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Closed [ 6 ] |
Fixed as SECURITY-988, copyartifact-1.44