[
https://issues.apache.org/jira/browse/NIFI-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387597#comment-15387597
]
Matt Gilman commented on NIFI-2244:
-----------------------------------
Updating the desired behavior... permissions on a connection should be driven
solely on the permissions on the source, destination, and parent process group.
> Cannot modify connection if user does not have permissions to modify source
> or destination
> ------------------------------------------------------------------------------------------
>
> Key: NIFI-2244
> URL: https://issues.apache.org/jira/browse/NIFI-2244
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
> Reporter: Mark Payne
> Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> A user is unable to modify a connection if its source or destination is a
> processor that is running. However, it appears that this logic is also
> applied when considering permissions. If I have permissions to modify a
> connection but the not permissions to modify the source or the destination,
> the UI does not allow me to Configure the connection with a right-click menu.
> Instead, the context menu shows "View Configuration" but the Operation
> palette menu allows me to configure the Connection (the palette vs. context
> menu issue is part of NIFI-2235).
> Also, along these lines we should only require the necessary permissions for
> various actions. For instance, component removal or updating it's position
> should not require read permissions. However, configuration of the component
> should require read permissions as it is necessary for obtaining the various
> property descriptors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
