[
https://issues.apache.org/jira/browse/MINIFICPP-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferenc Gerlits updated MINIFICPP-2229:
--------------------------------------
Description:
The flow definition (config.yml) file can already be encrypted, but this is
optional. Sensitive properties should always be written to the flow definition
file in encrypted form. All processor and controller service properties should
be marked with a flag that shows if they are sensitive.
If full-flow-definition-encryption is enabled, the flow definition file as a
whole can also be encrypted on top of this (as it is now), but the two
encryptions should use separate keys.
was:
The flow definition (config.yml) can already be encrypted, but this is
optional. Sensitive properties should always be written to the flow definition
file in encrypted form. All processor and controller service properties should
be marked with a flag that shows if they are sensitive.
If full-flow-definition-encryption is enabled, the flow definition file as a
whole can also be encrypted on top of this (as it is now), but the two
encryptions should use separate keys.
> Encrypt sensitive properties in the flow definition
> ---------------------------------------------------
>
> Key: MINIFICPP-2229
> URL: https://issues.apache.org/jira/browse/MINIFICPP-2229
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Ferenc Gerlits
> Assignee: Ferenc Gerlits
> Priority: Minor
>
> The flow definition (config.yml) file can already be encrypted, but this is
> optional. Sensitive properties should always be written to the flow
> definition file in encrypted form. All processor and controller service
> properties should be marked with a flag that shows if they are sensitive.
> If full-flow-definition-encryption is enabled, the flow definition file as a
> whole can also be encrypted on top of this (as it is now), but the two
> encryptions should use separate keys.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
