You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2021/10/27 02:20:00 UTC

[jira] [Assigned] (NIFI-6825) Allow sensitive flow details to be retrieved from a secret store (Hashicorp Vault)

     [ https://issues.apache.org/jira/browse/NIFI-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann reassigned NIFI-6825:
--------------------------------------

    Assignee: David Handermann  (was: Troy Melhase)

> Allow sensitive flow details to be retrieved from a secret store (Hashicorp Vault)
> ----------------------------------------------------------------------------------
>
>                 Key: NIFI-6825
>                 URL: https://issues.apache.org/jira/browse/NIFI-6825
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Troy Melhase
>            Assignee: David Handermann
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> {quote}Hashicorp Vault controller service
> {quote}
> {quote}Dynamic property descriptors - key (component PD identifier) / value (Vault identifier/location)
> {quote}
> {quote}Components can reference controller service to populate property descriptors directly
> {quote}
> {quote}Scenarios:
> {quote}
> {quote}1. NiFi config values are stored in Vault & accessed via HVSPP
> {quote}
> {quote}2. NiFi flow details are stored in Vault & accessed via HVCS; config values are not
> {quote}
> {quote}3. Both are stored in Vault & accessed with HVSPP & HVCS
> {quote}
> {quote}1. Refactor common code out of the HVSPP to "VaultCommunicationService" (framework level)
> {quote}
> {quote}2. HVSPP delegates/wraps HVCommSvc (framework level)
> {quote}
> {quote}3. HVCS delegates/wraps HVCommSvc (extension level)
> {quote}



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