You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Yolanda M. Davis (JIRA)" <ji...@apache.org> on 2017/04/26 13:50:05 UTC

[jira] [Reopened] (NIFI-3695) Create Node Manager & Notification Utilities

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

Yolanda M. Davis reopened NIFI-3695:
------------------------------------

chatted with [~mcgilman] offline and he highlighted a need to ensure we can identify and authorize a user executing a notification or node management request (instead of preauthorizing a node to perform those functions).  I'm reopening this ticket so that I can add an option to provide a proxy/user DN.  For secured nodes and clusters it would require an administrator to preset policy to a) allow a node to serve as a proxy and b) to identify and authorize a user to access the controller (which will support all operations from both tools).

> Create Node Manager & Notification Utilities
> --------------------------------------------
>
>                 Key: NIFI-3695
>                 URL: https://issues.apache.org/jira/browse/NIFI-3695
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Tools and Build
>            Reporter: Yolanda M. Davis
>            Assignee: Yolanda M. Davis
>             Fix For: 1.2.0
>
>
> The node manager utility should allow system administrators to connect, disconnect or remove a node from a cluster on the command line.  If a node is not part of a cluster an error message should display if node is not part of a cluster.  If a node is disconnected from a cluster and needs to be connected or removed from that cluster the tool should support receiving a list of urls to connected nodes which can be used to send the required command to the active cluster. 
> The notification utility should allow administrators to send messages as bulletins to the NiFi with levels of INFO, WARN or ERROR.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)