[ https://issues.apache.org/jira/browse/NIFI-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Grey resolved NIFI-4627. ----------------------------- 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 > Add support for NiFi Registry properties files to TLS-toolkit in nifi-toolkit > ----------------------------------------------------------------------------- > > Key: NIFI-4627 > URL: https://issues.apache.org/jira/browse/NIFI-4627 > Project: Apache NiFi > Issue Type: Improvement > Reporter: Kevin Doran > Assignee: Kevin Doran > Priority: Minor > > Currently, when running the TLS-toolkit in standalone mode there is an option > to specify a nifi.properties file to update, where the updated version > containing the keystore and truststore files will be written in the output > directory for each hostname. > Because the admin guide for NiFi Registry will include instructions for how > to use the NiFi toolkit for generating keys/certs, it would be nice that if a > user passes a NiFi Registry properties file path to the --nifiPropertiesFile > argument, the TLS tool will gracefully understand that and output an updated > NiFiRegistry properties file. -- This message was sent by Atlassian Jira (v8.20.10#820010)