[
https://issues.apache.org/jira/browse/NIFI-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413888#comment-15413888
]
Matt Gilman commented on NIFI-1781:
-----------------------------------
[~jameswing] In order to upload a template, the user must be authorized to do
so. We could have done this by introducing an authorization rule for uploading
templates, but we decided to attempt to create some consistency around how
templates enter the system. In order to create a template, the user needs to
have read permissions to every selected component and write permissions to the
current Process Group. So we've opted to require write permissions to the
Process Group that holds the Template for uploading as well. So we've decreased
the scope of template creation (Process Group level vs Global level). However,
they can still be utilized in a global perspective (viewing, instantiation,
etc).
Additionally, the Process Group will be used to fall back if other
authorizations fail. I don't believe this is happening right now so I've
created a JIRA for it [1].
[1] https://issues.apache.org/jira/browse/NIFI-2530
> Update UI to reflect component level authorization
> --------------------------------------------------
>
> Key: NIFI-1781
> URL: https://issues.apache.org/jira/browse/NIFI-1781
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Fix For: 1.0.0, 1.0.0-Beta
>
> Attachments: 0001-NIFI-1781.patch, nifi-component-samples.png,
> nifi-sample-flow.png
>
>
> - Update to UI to visual access level per component
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
