[
https://issues.apache.org/jira/browse/NIFI-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Grey resolved NIFI-2786.
-----------------------------
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 doesn't support -outputDirectory property in all modes
> ------------------------------------------------------------------
>
> Key: NIFI-2786
> URL: https://issues.apache.org/jira/browse/NIFI-2786
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 1.0.0
> Reporter: Andrew Grande
> Priority: Minor
> Labels: tls-toolkit
>
> TLS toolkit has 3 modes:
> # standalone
> # server (host a CA authority server)
> # client (remotely interact with CA authority server)
> There is an -o option to dump all artifacts (config, keystore, truststore) in
> a dedicated directory (default is . ). However, it's not a supported property
> for server and client mode.
> This is most useful for 'client' mode. When running on a remote workstation
> to create new certs signed by a NiFi CA authority, quite a few files are
> saved. If I need to generate multiple certs for multiple people I would have
> to manually move files out of the way (otherwise they are overwritten).
> Expected: add -o/--outputDirectory to the client mode (maybe server too).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
