[
https://issues.apache.org/jira/browse/NIFI-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Grey resolved NIFI-5365.
-----------------------------
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
> TLS Toolkit should handle NiFi Registry
> ---------------------------------------
>
> Key: NIFI-5365
> URL: https://issues.apache.org/jira/browse/NIFI-5365
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Tools and Build
> Affects Versions: 1.7.0
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Major
> Labels: keystore, registry, security, tls
>
> The TLS Toolkit should generate TLS material for the NiFi Registry.
> The necessary improvements include:
> * the tool should respect the input filename and not generate a hard-coded
> {{nifi.properties}} file as output; if the input file is
> {{nifi-registry.properties}} and no output filename is provided as an
> argument, the output file should be {{nifi-registry.properties}} as well
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
