[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858061#comment-15858061
]
ASF GitHub Bot commented on NIFI-3251:
--------------------------------------
GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/1483
NIFI-3251: Addressing JS error preventing CS table loading
NIFI-3251:
- Ensuring read permissions to the ControllerService before attempting to
check permissions to parent.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mcgilman/nifi NIFI-3251-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1483.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1483
----
commit a7d9702632b81a9e76eaecb3b377d2ad2e7037ba
Author: Matt Gilman <[email protected]>
Date: 2017-02-08T14:35:35Z
NIFI-3251:
- Ensuring read permissions to the ControllerService before attempting to
check permissions to parent.
----
> 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.15#6346)