You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andy LoPresto (JIRA)" <ji...@apache.org> on 2018/08/22 04:13:00 UTC

[jira] [Updated] (NIFI-5540) NiFi does not start in cluster mode without sensitive key explicitly defined

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

Andy LoPresto updated NIFI-5540:
--------------------------------
    Status: Patch Available  (was: In Progress)

> 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)