[
https://issues.apache.org/jira/browse/NIFI-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522637#comment-16522637
]
Andy LoPresto edited comment on NIFI-5335 at 6/25/18 6:19 PM:
--------------------------------------------------------------
Just noting here that if flowfiles are coming in with different keys used for
encryption, to avoid multiple instances of the {{EncryptContent}} processor,
some of these values might be good to read from flowfile attributes (i.e. an
{{UpdateAttribute}} processor could be used earlier in the flow to say
"Flowfile X from {{GetHDFS}} processor 1 is encrypted with key *K1*, while
Flowfile Y from {{FetchS3}} processor 2 is encrypted with key *K2*" and allow
for dynamic retrieval). The various passphrases would need to be maintained
somewhere though (possibly in variable registry).
was (Author: alopresto):
Just noting here that if flowfiles are coming in with different keys used for
encryption, to avoid multiple instances of the {{EncryptContent}} processor,
some of these values might be good to read from flowfile attributes (i.e. an
{{UpdateAttribute}} processor could be used earlier in the flow to say
"Flowfile X from {{GetHDFS}} processor 1 is encrypted with key *K1*, while
Flowfile Y from {{FetchS3}} processor 2 is encrypted with key *K2*" and allow
for dynamic retrieval. The various passphrases would need to be maintained
somewhere though (possibly in variable registry).
> PGP processor cannot handle multiple passworded keys in a pgp keyring.
> ----------------------------------------------------------------------
>
> Key: NIFI-5335
> URL: https://issues.apache.org/jira/browse/NIFI-5335
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration Management
> Affects Versions: 1.5.0
> Environment: RHEL
> Reporter: Bill SAndman
> Assignee: Andy LoPresto
> Priority: Major
> Attachments: EncryptContent.JPG
>
>
> The Encrypt Content processor can handle only one passworded PGP Secret key
> on a given keyring.
> To decrypt files from multiple data sources with different passworded PGP
> Secret Keys, we are forced to create a separate key ring for each data
> source, containing a single passworded PGP Secret Key.
> It would be optimal to be able to point the decryption processor at a single
> NIFI user keyring that had multiple data source Secret Keys, each passworded.
> We would then be able to pass either the SEC ID (eg; 1024D/671D6CAF or the
> UID (eg. dunnhumby - SMG - Prod) and the password for the given Secret Key.
> Ideally the attached image would also include a Private Key Identifier to
> distinguish which jey on the ring to use, that would match the Private
> Keyring Passphrase.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
