[
https://issues.apache.org/jira/browse/NIFI-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836647#comment-17836647
]
ASF subversion and git services commented on NIFI-13025:
--------------------------------------------------------
Commit 0e4b33ce4c7db001d746fc61b94170752fd67987 in nifi's branch
refs/heads/support/nifi-1.x from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0e4b33ce4c ]
NIFI-13025 Removed custom validation from NifiRegistryFlowRegistryClient
- NiFi Registry REST API enforces TLS handshake requirements
This closes #8629
Signed-off-by: David Handermann <[email protected]>
(cherry picked from commit cc7af91f97dd1844cc6c8d30bd47d6865cb20aaa)
> NifiRegistryFlowRegistryClient to allow for truststore only SSL Context
> Service
> -------------------------------------------------------------------------------
>
> Key: NIFI-13025
> URL: https://issues.apache.org/jira/browse/NIFI-13025
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Labels: backport-needed
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Right now the NifiRegistryFlowRegistryClient Registry Client, when configured
> with an SSL Context Service, requires the SSL CS to be configured with both a
> keystore and a truststore. However, there are valid deployment scenarios
> where only a truststore should be configured in case anonymous access to the
> Registry is desired.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
