[
https://issues.apache.org/jira/browse/NIFI-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Grey resolved NIFI-5461.
-----------------------------
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 populate generated client certificate DN into
> authorizers.xml if requested
> ---------------------------------------------------------------------------------------------
>
> Key: NIFI-5461
> URL: https://issues.apache.org/jira/browse/NIFI-5461
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Configuration, Security, Tools and Build
> Affects Versions: 1.7.1
> Reporter: Andy LoPresto
> Priority: Major
> Labels: authentication, authorization, certificate, client, pki,
> security, tls, tls-toolkit
>
> When initially configuring the {{authorizers.xml}}, it can be difficult
> because the *Initial Admin Identity* must be exactly the same as the
> Distinguished Name (DN) from the generated client certificate. Spaces in the
> DN can make this especially hard. The TLS Toolkit should have a command-line
> option which instructs it to generate an {{authorizers.xml}} with the client
> DN populated as the *IAI* in every necessary location.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
