[
https://issues.apache.org/jira/browse/NIFI-16430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124408#comment-18124408
]
ASF subversion and git services commented on NIFI-16430:
--------------------------------------------------------
Commit 8e973b54cdaefacef9853c86f53c22466f14a363 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8e973b54cda ]
NIFI-16430 Switched to WebClientService for Splunk Service.send (#11764)
* NIFI-16430 Switched to WebClientService for Splunk Service.send
- Extended Splunk SDK Service in WebClientSplunkService
- Added ConfiguredHostTrustManager to support TLS in Splunk Cloud
- Removed Class Loader isolation from Splunk Processors
> Switch to WebClientService for Splunk Service Send Method
> ----------------------------------------------------------
>
> Key: NIFI-16430
> URL: https://issues.apache.org/jira/browse/NIFI-16430
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The Splunk Processors use the Splunk SDK Service.send() method to communicate
> with Splunk Services over HTTP. The SDK implementation uses the standard Java
> HttpsURLConnection, which is not optimal for connection reuse and
> configuration. To provide better managed behavior, the Service.send() method
> should be overridden in a custom subclass and use the NiFi
> {{WebClientService}} abstraction for HTTP communication. This approach
> supports removing the need for Class Loader isolation with custom {{SSL
> Context Service}} configuration, and also supporting hostname-based
> verification for TLS communication with Splunk Cloud.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
