You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andy LoPresto (JIRA)" <ji...@apache.org> on 2017/05/17 16:03:04 UTC

[jira] [Created] (NIFI-3929) Allow external key management for EncryptContent processor

Andy LoPresto created NIFI-3929:
-----------------------------------

             Summary: 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


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
(v6.3.15#6346)