[
https://issues.apache.org/jira/browse/NIFI-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Grey resolved NIFI-5923.
-----------------------------
Resolution: Won't Do
In a recent mailing list discussion [1], a consensus discussion was made to
deprecate the module "nifi-toolkit-tls". A set of tickets [2] [3] [4] was
opened and resolved to carry out this work.
In order to complete this effort, any open tickets in the NIFI project relating
to defects, enhancements, etc of "nifi-toolkit-tls" should be marked resolved.
[1] https://lists.apache.org/thread/vn1nzobtz4fh7fs461sgg8jj9zygrk0f
[2] NIFI-12169 - Documentation updates to provide alternatives to usage of TLS
Toolkit
[3] NIFI-12200 - Remove nifi-toolkit-tls module
[4] NIFI-12201 - Deprecation markings for nifi-toolkit-tls module in
support/nifi-1.x
> Nifi tls toolkit in client mode should have option to output nifi.properties
> ----------------------------------------------------------------------------
>
> Key: NIFI-5923
> URL: https://issues.apache.org/jira/browse/NIFI-5923
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Nimrod Avni
> Priority: Minor
> Labels: Cerificate, Security, TLS, toolkit
>
> When using the nifi toolkit to setup my secured cluster, I noticed there is
> a big difference from when using it in server/client mode then using it in
> standalone mode. The client mode does not have the option to output a
> nifi.properties file like the standalone mode offers.
> The standalone mode offers an easy deployment after generating the
> certificate, while the client mode requires tedious copying of the security
> properties from the config.json file into the nifi.properties
> My suggestions are:
> * Have better documentation on the config.json file, how to use it, it's
> structure and so one
> * Have a flag when using the tls toolkit in client mode to generate a
> nifi.properties file from a base nifi.properties file or a brand new one
> (same as standalone mode)
> * Or, alternatively, have the option to configure nifi to read security
> properties from the config.json file instead of the nifi.properties file,
> allowing for easier deployment
> It would be great if these features will be added to the nifi toolkit.
> This discussion on the hortonworks forum
> ([https://community.hortonworks.com/questions/231221/nifi-security-configuration.html])
> can be used for reference of the problem
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
