Splunk Dev

I changed Splunk from using SSLv3 to TLSv1.2, and the Splunk Java SDK will not connect..

bosburn_splunk
Splunk Employee
Splunk Employee

I changed Splunk to use TLSv1.2 and disabled SSLv3, now my java portlet using the Java SDK will no longer connect. Why?

OR

I upgraded to the Java 8u31 (which was recently released) and they disabled SSLv3. My apps no longer connect. Why?

Tags (4)

ntbahriti_splun
Splunk Employee
Splunk Employee

With the Splunk SDK version 1.4.0 you don't need to modify, compile and repackage the HttpService.java in the JAR.
There are explanations and a working code example, last paragraph at:
http://answers.splunk.com/answers/209379/no-appropriate-protocol-protocol-is-disabled-or-ci.html#ans....

bosburn_splunk
Splunk Employee
Splunk Employee

By default, the Splunk Java SDK will use SSLv3 to connect. You will need to change this to TLS per the following instructions. This will be changed in a future release.

You will have to modify HttpService.java and change the following lines:

SSLContext context = SSLContext.getInstance("SSL");
to
SSLContext context = SSLContext.getInstance("TLSv1.2");

public static final String[] PROTOCOLS = {"SSLv3"};
to
public static final String[] PROTOCOLS = {"TLSv1.2"};

You will have to recompile the jar and redeploy it as well.

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...