[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836667#comment-15836667
]
ASF GitHub Bot commented on NIFI-3251:
--------------------------------------
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/1399
@mcgilman I think this looks good, it worked well in my testing. The
integration tests are passing again. These changes didn't break any tests, but
none of the tests in nifi-web-api really exercise them, and the test framework
does not make it easy to add something for this. At the risk of being a bad
committer, I merged anyways.
Thanks for contributing this.
> Users who do not have modify the component access policy for a process group
> should not be able to delete components.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3251
> URL: https://issues.apache.org/jira/browse/NIFI-3251
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Affects Versions: 1.1.0
> Reporter: Matthew Clarke
> Assignee: Matt Gilman
> Priority: Minor
> Fix For: 1.2.0
>
>
> Users are required to have "modify the component" access policy granted to
> them on a process group in which they want to add components to the canvas.
> They are not however required to have this access policy in order to remove
> components from the canvas. If a user is granted the "modify the component"
> access policy on a specific processor, that user can then delete that
> processor. The "modify the component" access policy when granted to a
> processor should only allow that user to modify the configuration (start,
> stop, disable, modify setting/properties). User should still be unable to
> delete that processor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
