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

Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2018/02/08 16:00:00 UTC

[jira] [Updated] (MINIFI-434) Preserve security properties when pulling a new config

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

Aldrin Piri updated MINIFI-434:
-------------------------------
    Fix Version/s: 0.5.0

> Preserve security properties when pulling a new config
> ------------------------------------------------------
>
>                 Key: MINIFI-434
>                 URL: https://issues.apache.org/jira/browse/MINIFI-434
>             Project: Apache NiFi MiNiFi
>          Issue Type: Improvement
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>             Fix For: 0.5.0
>
>
> Situation (secured instances)
> MiNiFi == (pull) ==> C2 server == (pull template) ==> NiFi cluster
> Template to pull contains a RPG to perform S2S between MiNiFi and NiFi cluster over HTTPS.
> When a new version of the template is pulled, security properties are removed and S2S cannot be performed until config is manually fixed and agent restarted.
> Security properties should probably be excluded in this config update process.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)