Develop Reference

How to validate TLS version from application client, not server

We are trying to validate what TLS version our web client application is using. We can run nmap --script ssl-enum-ciphers -p 443 www.example.com as we see TLS version 1.2 (That's the version we want.) However we are wanting to validate what version of TLS is being used from web application client directly? Not the server. This is a 1.6 java application that is deployed on Weblogic. Is this request possible to validate on the application directly? I see a lot of threads validating at the server level or the or validating what the server end, not the client application level.

How to get TLS version and applicable cipher suits from Http Request

I am using Twilio sandbox environment for testing WhatsApp integration with my application. As I moved application to different server twilio API is sending Error 20426 Upgrade Required.
Application was working fine on previous server. TLS version on both the server is 1.2 and SSL version is 3. Cipher Suits are also present on both servers as List provided in Twilio document. The only difference between two servers is the OS. On server where application is working OS installed is Linux and where application is not working OS is AIX 7.

Tomcat application as a client to another server using TLSv1.2

We have a Tomcat based Infra monitoring application which will connect to other servers and monitor / alert etc.
However , some of our servers are using TLSv1.2 only and seems that the monitoring application is only using the TLSv1 to connect which is having a slight issue.
We are currently doing a workaround by using http port to mornitor but for long term we would like to use the TLSv1.2.
Is there a way to force Tomcat to connect to other applications via TLSv1.2 only?
Thanks
Using Tomcat 7 and Java 1.7.

The documentation for the SunJSSEProvider says:
Although SunJSSE in the Java SE 7 release supports TLS 1.1 and TLS
1.2, neither version is enabled by default for client connections. Some servers do not implement forward compatibility correctly and
refuse to talk to TLS 1.1 or TLS 1.2 clients. For interoperability,
SunJSSE does not enable TLS 1.1 or TLS 1.2 by default for client
connections.
So TLS 1.2 is there, it just isn't enabled. To enable it add something like
-Dhttps.protocols=TLSv1.1,TLSv1.2
to the startup-parameters of your tomcat. Then it should be able to speak TLS 1.2 as well as TLS 1.1. If you need any older protocols you can also add them as described in the linked documentation.

ActiveMQ HTTP transport protocol not able to create ActiveMQSession on Java 8

I was using ActiveMQ 5.9.0 using HTTP transport protocol with Java 7. After I migrate from Java 7 to Java 8, my producer program is not able to create session to the broker. It keeps on trying to get the ActiveMQSession.

That version is very old and likely will have several issues with Java 8 not just in HTTP transport but other areas as well. The version of Jetty used in that broker is definitely not Java 8 compatible, you need to move to the latest release v5.14.2 which should work under Java 8 although the official Java 8 supported broker is the next major release v5.15.0

Server Name Indication support for java 1.6

I want to add SNI support for my server build on java. After googling i found that java 1.8 have the support in Server side. Is there any library or patch to support SNI in server side for java 1.6?

I created patch for JSSE to support SNI in java 7.
https://github.com/jvenugopal/jsse-sni-patch