You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2018/03/21 14:29:00 UTC

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

     [ https://issues.apache.org/jira/browse/NIFI-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Gilman updated NIFI-4885:
------------------------------
    Status: Patch Available  (was: Reopened)

> 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
>             Fix For: 1.6.0
>
>
> 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)