[
https://issues.apache.org/jira/browse/NIFI-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415323#comment-15415323
]
ASF GitHub Bot commented on NIFI-2530:
--------------------------------------
GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/826
Template Authorization - defer to parent Process Group when no explicit
policy is defined
NIFI-2530:
- When no explicit policy is defined, defer to the parent Process Group
instead of attempting to match component's within the flow.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mcgilman/nifi NIFI-2530
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/826.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 #826
----
commit e21049ceadd8df1154fd1dbaa236ca8b1a7800f1
Author: Matt Gilman <[email protected]>
Date: 2016-08-10T14:08:04Z
NIFI-2530:
- When no explicit policy is defined, defer to the parent Process Group
instead of attempting to match component's within the flow.
----
> 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)
