[
https://issues.apache.org/jira/browse/NIFI-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Grey resolved NIFI-5462.
-----------------------------
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
> Refactor TLS Toolkit
> --------------------
>
> Key: NIFI-5462
> URL: https://issues.apache.org/jira/browse/NIFI-5462
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Security, Tools and Build
> Affects Versions: 1.7.1
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Major
> Labels: certificate, nifi-registry, pki, refactor, registry,
> security, tls-toolkit
>
> The TLS Toolkit was originally designed with limited scope and has since
> grown organically to meet additional requirements. Because of this, its
> components can be disjoint, there is unnecessary code and communication
> interfaces, and it can be difficult to extend.
> A complete refactor should be performed to remove superfluous code, make it
> easier to extend, separate concerns (command-line interaction, certificate
> generation and signing, and component communication [client/server,
> internal/external]).
> Along with this refactor, it should be extended to handle additional
> components which require certificate generation, signing, and trust
> allocation, such as the Apache NiFi Registry.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
