[ 
https://issues.apache.org/jira/browse/NIFI-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417108#comment-15417108
 ] 

ASF GitHub Bot commented on NIFI-2501:
--------------------------------------

GitHub user mcgilman opened a pull request:

    https://github.com/apache/nifi/pull/835

    Ensuring users can access the Controller Service and Reporting Tasks lists

    NIFI-2501:
    - Ensuring users can access the controller service list regardless of 
permissions on the corresponding process group or controller.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mcgilman/nifi NIFI-2501

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/835.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 #835
    
----
commit 8e99c338c17d08ee465f9fac9f178cc8127f20ee
Author: Matt Gilman <[email protected]>
Date:   2016-08-10T18:52:59Z

    NIFI-2501:
    - Ensuring users can access the controller service list regardless of 
permissions on the corresponding process group or controller.

----


> UI - Process Group configuration requires write permissions
> -----------------------------------------------------------
>
>                 Key: NIFI-2501
>                 URL: https://issues.apache.org/jira/browse/NIFI-2501
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>            Reporter: Matt Gilman
>            Assignee: Matt Gilman
>             Fix For: 1.0.0
>
>
> Since Controller Services are accessed through the Process Group 
> configuration, we need to allow users without read/write permissions to 
> access that dialog in case they do have permissions to a controller service 
> in there. The Controller settings dialog is already updated to support this 
> case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to