[
https://issues.apache.org/jira/browse/NIFI-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414248#comment-15414248
]
Joseph Witt commented on NIFI-2530:
-----------------------------------
[~mcgilman] It seems to me that permissions of the templates really only need
to be #1 or #3. The concept of #2 applying I'm not sure makes sense. We're
not talking about 'the instance of those components' on the flow but rather a
template/snapshot of that item. #1 allows specific templates to be locked down
if needed and #3 provides sensible defaults. But #2 is extending the concept
of a 'component' to be both its actual instance on a flow and also any 'copies'
of it made as templates.
Do you agree?
> Template authorization - Fall back to Process Group
> ---------------------------------------------------
>
> Key: NIFI-2530
> URL: https://issues.apache.org/jira/browse/NIFI-2530
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Blocker
> Fix For: 1.0.0
>
>
> Template authorization strategy in order:
> 1 - Explicit policy on template
> 2 - Authorize based on permissions of underlying components
> 3 - Authorize based on parent Process Group
> Currently, only 1 and 2 are checked. Need to fall back to parent Process
> Group.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
