[ https://issues.apache.org/jira/browse/NIFI-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Grey resolved NIFI-3265. ----------------------------- 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 client can fail when tls-toolkit server has multiple cn attributes > ------------------------------------------------------------------------------ > > Key: NIFI-3265 > URL: https://issues.apache.org/jira/browse/NIFI-3265 > Project: Apache NiFi > Issue Type: Bug > Affects Versions: 1.1.1, 1.0.1 > Reporter: Bryan Rosander > Priority: Minor > Labels: tls-toolkit > > Ldap hierarchies can have multiple cn attributes. > tls-toolkit in client mode validates the first CN attribute parsed from the > distinguished name against the hostname name of the tls-toolkit server to > help avoid man-in-the-middle attacks. > This check can fail when multiple CN attributes are present. -- This message was sent by Atlassian Jira (v8.20.10#820010)