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

Joseph Gresock commented on NIFI-8445:
--------------------------------------

I believe the analogous Spring Vault method would be 
[encrypt|https://docs.spring.io/spring-vault/docs/current/api/org/springframework/vault/core/VaultTransitOperations.html#encrypt-java.lang.String-org.springframework.vault.support.Plaintext-]
 rather than 
[write|https://docs.spring.io/spring-vault/docs/current/api/org/springframework/vault/core/VaultTemplate.html#write-java.lang.String-java.lang.Object-],
 but I notice encrypt does take a Plaintext, which wraps bytes[].

> Implement HashicorpVaultCommunicationService
> --------------------------------------------
>
>                 Key: NIFI-8445
>                 URL: https://issues.apache.org/jira/browse/NIFI-8445
>             Project: Apache NiFi
>          Issue Type: Sub-task
>            Reporter: Joseph Gresock
>            Priority: Minor
>
> Suggest using Spring's VaultTemplate to expose an initial set of 
> Vault-related methods that can be later expanded. 
> Should take the following configuration:
>  # Vault address (e.g., [https://localhost:8200|https://localhost:8200/])
>  # TLS configuration (used only if address is https)
>  # Properties file location for configuring Vault Authentication Method
> Should expose the initial methods:
>  * encrypt(String transitKey, String plainText)
>  * decrypt(String transitKey, String cipherText)
> This service should be able to be used initially in the NiFi core code and 
> Encrypt-Config tool code, and should eventually be made available to the NiFi 
> Registry code.



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

Reply via email to