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

ASF GitHub Bot commented on NIFI-3594:
--------------------------------------

Github user markap14 commented on the issue:

    https://github.com/apache/nifi/pull/1686
  
    @alopresto one thought regarding the StaticKeyProvider... rather than 
having a .key=<hex> perhaps it would make sense to instead use a 
.key.<key_id>=<hex> property scheme. This would allow multiple Key ID's to be 
used, which would resolve the 'Potential Issue' listed above, of now allowing 
the key to rotate, with rather minimal changes to the code??


> Implement encrypted provenance repository
> -----------------------------------------
>
>                 Key: NIFI-3594
>                 URL: https://issues.apache.org/jira/browse/NIFI-3594
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Core Framework
>    Affects Versions: 1.1.1
>            Reporter: Andy LoPresto
>            Assignee: Andy LoPresto
>              Labels: encryption, provenance, repository
>
> I am going to start with the provenance repository, as the new implementation 
> of {{WriteAheadProvenanceRepository}} has the most recent design decisions 
> and has not been available in a released version yet, so there should be 
> minimal backward compatibility concerns. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to