[
https://issues.apache.org/jira/browse/NIFI-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174639#comment-15174639
]
ASF GitHub Bot commented on NIFI-1420:
--------------------------------------
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/233#issuecomment-190970047
Whenever an SSL context is being created (done 4 times in multiple
different classes) "SSLContextService.ClientAuth.REQUIRED" is used. Should we
offer configuration options for this? For PutSplunk and GetSplunk I can
understand it because we are requiring the server to provide authorization but
maybe someone using ListenSplunkForwader doesn't need it to verify who's
sending the data.
> Splunk Processors
> -----------------
>
> Key: NIFI-1420
> URL: https://issues.apache.org/jira/browse/NIFI-1420
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 0.6.0
>
>
> To continue improving NiFi's ability to collect logs, a good integration
> point would be to have a processor that could listen for data from a Splunk
> forwarder (https://docs.splunk.com/Splexicon:Universalforwarder). Being able
> to push log messages to Splunk would also be useful.
> Splunk provides an SDK that may be helpful:
> https://github.com/splunk/splunk-sdk-java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
