[ 
https://issues.apache.org/jira/browse/NIFI-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522656#comment-16522656
 ] 

Bill SAndman commented on NIFI-5335:
------------------------------------

Andy,

Thanks for picking this up so quickly. Vik has friends in High places.

>From our side we would expect multiple instances of the EncryptProcessor as 
>you noted. Is that a bad way to view the Nifi world? We would expect each 
>password would be stored in that EncryptProcessor instance. However your 
>thoughts would also be a valid method

Please let me know if I can get you any more information.

Sandman

> 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)

Reply via email to