[
https://issues.apache.org/jira/browse/NIFI-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-5627.
------------------------------------
Resolution: Delivered
> Improve handling of sensitive properties
> ----------------------------------------
>
> Key: NIFI-5627
> URL: https://issues.apache.org/jira/browse/NIFI-5627
> Project: Apache NiFi
> Issue Type: Epic
> Components: Configuration, Core Framework
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Major
> Labels: component-versioning, encryption, properties, registry,
> security, sensitive, variable
>
> There are a number of disparate issues around the handling of _sensitive
> properties_.
> There should be a clear naming strategy to differentiate:
> 1. component properties that are sensitive ({{InvokeHTTP}} password,
> {{EncryptContent}} password etc.)
> 1. secret framework configuration values ({{nifi.sensitive.props.key}},
> {{nifi.security.keystorePasswd}}, LDAP Manager password, etc.)
> This epic regards the first.
> In addition:
> * Sensitive component properties should be handled in Expression Language
> * Sensitive component properties should be versionable in conjunction with
> NiFi Registry (this requires distributed key management)
> * Dynamic property descriptors on components should be able to be marked as
> sensitive
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
