[
https://issues.apache.org/jira/browse/NIFI-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386973#comment-15386973
]
ASF GitHub Bot commented on NIFI-2244:
--------------------------------------
GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/698
Updating the UI to reflect the access policies being enforced
NIFI-2244:
- Separating the access control check and the supports modification check
for the selected component.
- Using separated access control check to support editing when possible
without write permission.
NIFI-2307:
- Adding support for opening Connection configuration and Connection
details dialog when source/destination permissions are not allowed.
- Enforcing connection permissions based on the source and destination
comonent.
- Removing connection specific access policies.
NIFI-2265:
- Filtering out sensitive details in component status and status history
when appropriate.
NIFI-1800:
- Adding parent process group id to the Controller Services table.
NIFI-2077:
- Removing some old un-used icons following the UI refresh.
NIFI-2242:
- Requiring write permissions for all components in a selection.
NIFI-2080:
- Updating style of the name in the selection context to handle scroll bars
and use available width.
NIFI-2331:
- Addressing issue when removing a user/group which was causing the tenant
policy to be removed.
NIFI-2335:
- Ensuring the flow is saved after starting/stopping a process group.
NIFI-2235:
- Ensuring we use consistent conditions between the context menu and the
operate palette.
- Allowing users with read only access to the tenants page.
- Fixing current user integration test.
- Ensuring schedule methods are locked appropriately.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mcgilman/nifi NIFI-2244
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/698.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 #698
----
commit f62f48efe5f0e68f6c6f439565a31c9ae4e708b7
Author: Matt Gilman <[email protected]>
Date: 2016-07-21T01:41:06Z
NIFI-2244:
- Separating the access control check and the supports modification check
for the selected component.
- Using separated access control check to support editing when possible
without write permission.
NIFI-2307:
- Adding support for opening Connection configuration and Connection
details dialog when source/destination permissions are not allowed.
- Enforcing connection permissions based on the source and destination
comonent.
- Removing connection specific access policies.
NIFI-2265:
- Filtering out sensitive details in component status and status history
when appropriate.
NIFI-1800:
- Adding parent process group id to the Controller Services table.
NIFI-2077:
- Removing some old un-used icons following the UI refresh.
NIFI-2242:
- Requiring write permissions for all components in a selection.
NIFI-2080:
- Updating style of the name in the selection context to handle scroll bars
and use available width.
NIFI-2331:
- Addressing issue when removing a user/group which was causing the tenant
policy to be removed.
NIFI-2335:
- Ensuring the flow is saved after starting/stopping a process group.
NIFI-2235:
- Ensuring we use consistent conditions between the context menu and the
operate palette.
- Allowing users with read only access to the tenants page.
- Fixing current user integration test.
- Ensuring schedule methods are locked appropriately.
----
> 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)
