Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16813

Check permission for parametized Project name instead of requiring global read

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • copyartifact-plugin
    • None

      When archiving from a dynamic project name it currently requires read permission on that project for all authenticated. In a corporate environments it means anyone in the corporation should be able to see that project.

      The goal would be to check that the current user has read access on the dynamically generated project.

      Currently without that security, we could use this plugin and make it safe in our configuration (we don't have per-project access rights).

          [JENKINS-16813] Check permission for parametized Project name instead of requiring global read

          wernight created issue -

          wernight added a comment -

          Would probably also fix JENKINS-13222

          wernight added a comment - Would probably also fix JENKINS-13222
          wernight made changes -
          Link New: This issue is related to JENKINS-13222 [ JENKINS-13222 ]

          Jesse Glick added a comment -

          Yes it just seems like a duplicate.

          Jesse Glick added a comment - Yes it just seems like a duplicate.
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147641 ] New: JNJira + In-Review [ 192511 ]
          ikedam made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Unassigned Unassigned
            wernight wernight
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: