[
https://issues.apache.org/jira/browse/MINIFI-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343947#comment-16343947
]
Pierre Villard commented on MINIFI-434:
---------------------------------------
I was looking into it and I suggest to make a change in
{{handleChange(InputStream)}} of {{MiNiFiConfigurationChangeListener}}. I guess
this concerns only the {{PullHttpChangeIngestor}} implementation and we could
add a property for this ingestor to let users decide if security properties
should be preserved or not. Thoughts?
> 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
> Priority: Major
>
> 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)
