[jira] [Commented] (NIFI-16184) Add TLS Endpoint Identification for Cluster Node Communication

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-16184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104170#comment-18104170 ] 

ASF subversion and git services commented on NIFI-16184:
--------------------------------------------------------

Commit 2e700201eb6fd16831be37689090976529634a6d in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2e700201eb6 ]

NIFI-16184 Add TLS Endpoint Identification for Cluster Communication (#11530)

> Add TLS Endpoint Identification for Cluster Node Communication
> --------------------------------------------------------------
>
>                 Key: NIFI-16184
>                 URL: https://issues.apache.org/jira/browse/NIFI-16184
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Current NiFi cluster node communication involves a separate socket communication with mutual TLS, in addition to HTTPS request replication for coordinated operations. FlowFile load balancing and cluster status communication do not use the HTTP protocol, but should enforce the same endpoint identification requirements as HTTPS request handling for consistency.
> Existing cluster configurations require DNS Subject Alternative Names that match peer hostnames for HTTPS request replication, so enabling endpoint identification for other cluster socket communication provides a unified handling strategy for all node-to-node TLS handshaking.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)