You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2021/03/01 16:00:00 UTC

[jira] [Updated] (NIFI-8230) Remove default Sensitive Properties Key

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

David Handermann updated NIFI-8230:
-----------------------------------
    Status: Patch Available  (was: In Progress)

Submitted PR with the following features:
 * Removed hard-coded default value for Sensitive Properties Key
 * Introduced conditional generation of random 32 character key using Base64 encoding without padding of 24 bytes from {{java.util.SecureRandom}}
 * Introduced error log and exception when the Sensitive Properties Key is null or blank and there is an existing Flow Configuration {{flow.xml.gz}}
 * The exception references the Administration Guide section on Migrating a Flow with Sensitive Properties

> Remove default Sensitive Properties Key
> ---------------------------------------
>
>                 Key: NIFI-8230
>                 URL: https://issues.apache.org/jira/browse/NIFI-8230
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Security
>    Affects Versions: 1.13.0
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Support for encryption of sensitive properties relies on configuration of the Sensitive Properties Key specified using {{nifi.sensitive.props.key}} in {{nifi.properties}}.  The default behavior of {{StringEncryptor}} allows for the key to be blank and falls back to a default value, logging a verbose error message indicating that an explicit key should be provided.
> The fallback to a default value for the Sensitive Properties Key should be removed and an exception should be thrown indicating that the property value is required.  Deployments that already have an explicit value will not be impacted.  Migration guidance for upgrading should include steps to encrypt the configuration using a new key.
> It may be worthwhile generating a random Sensitive Properties Key for new installations where there is no existing flow.  This would new standalone installations to run with a secure key without the need for manual steps.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)