Splunk Dev

How to enforce TLS v1.2 in Java program talking to Splunk server via log4j2 ?

maciej_kw
Engager

I am trying to get our Java client application talking to a Splunk server provided by one of our vendors.
The communication is supposed to be simple. Our client app will send just plain text messages once a while.
I am using log4j2 as a platform for communication with the Splunk server.
Below are Splunk related appender and logger defined in the log4j2.xml file.
Vendor claims they do not receive messages from us.
However they see some traffic originating from our server where the application runs.
They suggest to enforce TLS v1.2 protocol on communication with their Splunk server.
How can we do that?
log4j2 configuration:

<Appenders>
    <Http name="httpSplunk"
                url="...some.server.com:8088/services/collector/event"
                token="some-token"
                host="$${env:COMPUTERNAME}"
                index=""
                source=""
                sourcetype=""
                middleware=""
                batch_size_bytes="10240"
                batch_size_count="10"
                batch_interval="1000"
                disableCertificateValidation="true">
        <PatternLayout pattern="%m"/>
    </Http>
</Appenders>
<Loggers>
    <Root level="warn">
        <AppenderRef ref="httpSplunk"/>
    </Root>
    <Logger name="splunk.Ellenby" level="info">
        <AppenderRef ref="httpSplunk"/>
    </Logger>
</Loggers>

Thank you

Best Regards,
Maciej Kwiecinski

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...