[
https://issues.apache.org/jira/browse/NIFI-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589180#comment-16589180
]
ASF GitHub Bot commented on NIFI-5540:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/2959
Verified that I am now able to start up a cluster without explicitly
specifying a sensitive properties key, same as it previously worked before this
issue, thanks Andy! Will merge shortly
> NiFi does not start in cluster mode without sensitive key explicitly defined
> ----------------------------------------------------------------------------
>
> Key: NIFI-5540
> URL: https://issues.apache.org/jira/browse/NIFI-5540
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.7.1
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Major
> Labels: config, encryption, security
>
> While the docs instruct users to explicitly set a value for
> {{nifi.sensitive.props.key}} in *nifi.properties* to use when encrypting
> sensitive component properties to persist in the *flow.xml.gz*, some users do
> not. Historically, these instances use a default, hardcoded key generation
> value.
> During the deprecation of {{StringEncryptor.createEncryptor(NiFiProperties)}}
> in NIFI-5376, the code which provided the default was missed in a specific
> cluster scenario.
> The default should be provided, and a warning should be printed to the app
> log if the provided key value is empty, in both standalone and cluster modes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
