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

ASF subversion and git services commented on NIFI-8511:
-------------------------------------------------------

Commit aedbd0d753a143361f46b813a566f35c722f9049 in nifi's branch 
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=aedbd0d ]

NIFI-8511 Added KeyStore implementation of KeyProvider

- KeyStoreKeyProvider supports PKCS12 and BCFKS
- Refactored KeyProvider and implementations to nifi-security-kms
- Updated Admin Guide and User Guide with KeyStoreKeyProvider details

NIFI-8511 Improved documentation and streamlined several methods

Signed-off-by: Nathan Gough <[email protected]>

This closes #5110.


> Add KeyStore Implementation of KeyProvider
> ------------------------------------------
>
>                 Key: NIFI-8511
>                 URL: https://issues.apache.org/jira/browse/NIFI-8511
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>              Labels: encryption, keystore, security
>          Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> The purpose of this issue is to create a new implementation of the 
> {{KeyProvider}} interface supported by an instance of 
> {{java.security.KeyStore}}.  This implementation should support configurable 
> KeyStore Location, Type, and Password properties in order for the 
> implementation to work with the types listed in the NiFi {{KeystoreType}} 
> enumeration.  The implementation should be capable of reading {{SecretKey}} 
> entries from the configured {{java.security.KeyStore}} and making them 
> available to calling components.  The approach should provide a more 
> standardized format for accessing {{SecretKey}} material to support encrypted 
> repository implementations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to