You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/06 15:03:00 UTC

[jira] [Commented] (NIFI-4885) More granular restricted component categories

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

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

GitHub user mcgilman opened a pull request:

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

    NIFI-4885: Granular component restrictions

    NIFI-4885: 
    - Introducing more granular restricted component access policies.
    - Current restricted components have been updated to use new granular restrictions.

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

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

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

    https://github.com/apache/nifi/pull/2515.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 #2515
    
----
commit 0610789f4e75f3983d54f75cec79e0a2bd8b7991
Author: Matt Gilman <ma...@...>
Date:   2018-02-16T21:21:47Z

    NIFI-4885:
    - Introducing more granular restricted component access policies.

----


> More granular restricted component categories
> ---------------------------------------------
>
>                 Key: NIFI-4885
>                 URL: https://issues.apache.org/jira/browse/NIFI-4885
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework, Core UI
>            Reporter: Matt Gilman
>            Assignee: Matt Gilman
>            Priority: Major
>
> Update the Restricted annotation to support more granular categories. Available categories will map to new access policies. Example categories and their corresponding access policies may be
>  * read-filesystem (/restricted-components/read-filesystem)
>  * write-filesystem (/restricted-components/write-filesystem)
>  * code-execution (/restricted-components/code-execution)
>  * keytab-access (/restricted-components/keytab-access)
> The hierarchical nature of the access policies will support backward compatibility with existing installations where the policy of /restricted-components was used to enforce all subcategories. Any users with /restricted-components permissions will be granted access to all subcategories. In order to leverage the new granular categories, an administrator will need to use NiFi to update their access policies (remove a user from /restricted-components and place them into the desired subcategory)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)