[
https://issues.apache.org/jira/browse/NIFI-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-3929.
------------------------------------
Resolution: Won't Do
> Allow external key management for EncryptContent processor
> ----------------------------------------------------------
>
> Key: NIFI-3929
> URL: https://issues.apache.org/jira/browse/NIFI-3929
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Andy LoPresto
> Priority: Major
> Labels: encryption, key-management, security
>
> Currently the {{EncryptContent}} processor (and a future {{EncryptAttribute}}
> processor) can only use a static key (or password-derived key) to
> encrypt/decrypt data. Similar to the {{KeyProvider}} interface used in the
> {{EncryptedWriteAheadProvenanceRepository}} that exposes multiple back-end
> implementations ({{StaticKeyProvider}}, {{FileBasedKeyProvider}}, etc.), a
> generic key management controller service is proposed in
> [NIFI-3890|https://issues.apache.org/jira/browse/NIFI-3890], and this
> processor should add support for consuming the CS and using it to dynamically
> access provided keys for encryption/decryption operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
