[
https://issues.apache.org/jira/browse/NIFI-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-5346.
------------------------------------
Fix Version/s: 1.14.0
Resolution: Fixed
Implemented in EncryptContentPGP and DecryptContentPGP with supporting
Controller Services.
> Allow EncryptContent processor to specify PGP key as processor property
> -----------------------------------------------------------------------
>
> Key: NIFI-5346
> URL: https://issues.apache.org/jira/browse/NIFI-5346
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.7.0
> Reporter: Andy LoPresto
> Assignee: David Handermann
> Priority: Major
> Labels: encryption, pgp, security
> Fix For: 1.14.0
>
> Time Spent: 11h
> Remaining Estimate: 0h
>
> Users have requested the capability to paste the ASCII-armored key contents
> into an {{EncryptContent}} processor property in order to decouple from from
> an external keyring (for both encryption and decryption).
> The private key would be protected as a sensitive property (encrypted in the
> flow.xml.gz the same as a password field). The public key can either be
> protected in the same way, or treated as a plaintext value (it is not
> sensitive). There should be an additional field to record the unique
> identifier of the respective key (i.e. key ID or fingerprint + description).
> Specifying all of this information may be confusing on the default processor
> property dialog, and so an "Advanced"/"PGP" custom UI should be provided
> which organizes this information in a helpful way.
> Obviously, encrypting with a literal public key or decrypting with a literal
> private key should be easily interoperable with another encryption/decryption
> operation (either with another instance of {{EncryptContent}} within NiFi
> referencing an external keyring or using an external tool like GnuPG).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
