NIFI-16184 Add TLS Endpoint Identification for Cluster Communication - #11530
Open
exceptionfactory wants to merge 1 commit into
Open
NIFI-16184 Add TLS Endpoint Identification for Cluster Communication#11530exceptionfactory wants to merge 1 commit into
exceptionfactory wants to merge 1 commit into
Conversation
exceptionfactory
force-pushed
the
NIFI-16184
branch
3 times, most recently
from
August 11, 2026 21:03
e8c5d05 to
bbc356f
Compare
exceptionfactory
force-pushed
the
NIFI-16184
branch
from
August 12, 2026 01:11
bbc356f to
9fc49be
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
NIFI-16184 Adds TLS Endpoint Identification using the
HTTPSalgorithm for cluster node communication, including status communication and FlowFile load balancing.The functional changes add
HTTPSas the Endpoint Identification Algorithm forSSLParameterswhen configuring TLS sockets. This strategy aligns with configuration requirements already in place for secure cluster communication. With existing cluster communication requiring DNS Subject Alternative Names on a certificate matching the requested hostname when replicating HTTP requests between cluster nodes, enforcing HTTPS Endpoint Identification for cluster protocol communication ensures consistency across node socket types.Additional tests exercise low-level parameters and existing system tests exercise secure cluster communication.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking
Pull Request Tracking
NIFI-00000NIFI-00000VerifiedstatusPull Request Formatting
mainbranchVerification
Please indicate the verification steps performed prior to pull request creation.
Build
./mvnw clean install -P contrib-checkLicensing
LICENSEandNOTICEfilesDocumentation