[
https://issues.apache.org/jira/browse/NIFIREG-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288592#comment-16288592
]
ASF GitHub Bot commented on NIFIREG-61:
---------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi-registry/pull/51
To be honest, if a "non-you" actor performs the merge, you don't have to
worry about this. Your fork's branch will maintain history automatically. The
master will be the squashed commit (usually cherry-picked onto the master
branch).
> Add support for encrypted properties in configuration files
> -----------------------------------------------------------
>
> Key: NIFIREG-61
> URL: https://issues.apache.org/jira/browse/NIFIREG-61
> Project: NiFi Registry
> Issue Type: New Feature
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Fix For: 0.0.1
>
>
> The NiFi Registry server is configured by files on disk, e.g.,
> nifi-registry.properties, bootstrap.conf, and XML files for loading
> extensions. Sometimes these files contain properties with sensitive values,
> such as credentials.
> We want to be able to support encrypting property values in NiFi Registry
> configuration files on disk that get decrypted in memory at runtime. As an
> initial step, the decryption key will be specified in the bootstrap.conf
> file. In the future, it might be input to the bootstrap processes via other
> means.
> For the design of this feature, the NiFi implementation of this capability
> should be used as a guide.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
