You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/09/17 13:33:00 UTC
[jira] [Commented] (NIFI-16354) Switch to Property Encryption Provider for MiNiFi C2 Flow Encryption
[ https://issues.apache.org/jira/browse/NIFI-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18116340#comment-18116340 ]
ASF subversion and git services commented on NIFI-16354:
--------------------------------------------------------
Commit d3781c0934603c6648f2fb765293af31497db830 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d3781c09346 ]
NIFI-16354 Switched MiNiFi C2 to Property Encryption Provider (#11689)
> Switch to Property Encryption Provider for MiNiFi C2 Flow Encryption
> --------------------------------------------------------------------
>
> Key: NIFI-16354
> URL: https://issues.apache.org/jira/browse/NIFI-16354
> Project: Apache NiFi
> Issue Type: Improvement
> Components: MiNiFi
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> MiNiFi C2 currently encrypts sensitive values in inbound flows with PropertyEncryptorBuilder and the sensitive properties key, rather than the Property Encryption Provider the application already initializes. This behavior should be changed so that StandardFlowPropertyEncryptor encrypts through that provider and SensitivePropertyCodec, using the same parameter and component contexts the framework uses when loading a flow, and wires C2 to FlowController.getPropertyEncryptionProvider(). C2 would then honor the configured provider and nifi-property-encryptor can be removed from the MiNiFi C2 modules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)