Skip to main content



Use TLSv1.2 and deactivate TLSv1 and TLSv1.1

Recently, I got in to a situation where my customer web service deactivated TLSv1 and TLSv1.1 protocol.

Eventually, my application client that used to interact with Server started receiving below error in hand-shake

javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure 

After analysis I found out that my application runs on JDK 1.5 that only supports TLSv1.

To replicate this scenario, I deployed web-service in tomcat  and made my tomcat to accept only TLSv1.2 protocol. This can be done by changing server.xml as follows:

<Connector ... SSLEnabled="true" sslProtocols="TLSv1.2" sslEnabledProtocols = "TLSv1.2" />

***Please note that it depends upon tomcat version to use which either of sslProtocols or sslEnabledProtocols attribute


Now when I ran my usual client application it received handshake failure as Client did Hello with TLSv1, while my server was not ready to accept it.

Possible solutions to update client were :

  • Update my application to JDK 8 , as it uses TLSv1.2 as default protocol. 
  • Update my application to JDK (, say 7) that supports TLSv1.2 protocol. Then set following system properties in client code.

System.setProperty("https.protocols","TLSv1.2");
System.setProperty("deployment.security.TLSv1", "false");
System.setProperty("deployment.security.TLSv1.2", "true");
System.setProperty("deployment.security.TLSv1.1", "false");
  
*** But  I noticed hat these properties work when my code was making normal URL Connections
  • My application was making SOAP call to server to using 2nd option actually didn't worked in my case. Client that my application has is using AXIS 1.4 code to invoke SOAP service. I explored possible solution to do in this case:
    • To write my class as follows :
public class TrustAllSSLSocketFactory extends JSSESocketFactory implements SecureSocketFactory {

public TrustAllSSLSocketFactory(Hashtable attributes) {

super(attributes);

}



@Override

protected void initFactory() throws IOException {



try {

SSLContext context = getContext();

sslFactory = context.getSocketFactory();

} catch (Exception e) {

if (e instanceof IOException) {

throw (IOException) e;

}

throw new IOException(e.getMessage());

}

}

protected SSLContext getContext() throws Exception {

/*String keystoreFile = (String) attributes.get("keystore");
String keystoreType = (String) attributes.get("keystoreType");
String keyPass = (String) attributes.get("keypass");

String protocol = (String) attributes.get("protocol");
 String algorithm = (String) attributes.get("algorithm");

 if(keystoreFile != null && keystorePass != null)
  KeyStore kstore = initKeyStore(keystoreFile, keystorePass);

com.sun.net.ssl.KeyManagerFactory kmf = com.sun.net.ssl.KeyManagerFactory.getInstance(algorithm);

kmf.init(kstore, keystorePass.toCharArray());


com.sun.net.ssl.TrustManager[] tm = null;

com.sun.net.ssl.TrustManagerFactory tmf = com.sun.net.ssl.TrustManagerFactory.getInstance("SunX509");
tmf.init(kstore);
tm = tmf.getTrustManagers();

SSLContext context = SSLContext.getInstance(protocol); 

context.init(kmf.getKeyManagers(), tm, new java.security.SecureRandom()); */

SSLContext context = SSLContext.getInstance("TSLv1.2"); 

context.init(null, null, null);
return context;

}

}

Updated client code to set following properties

AxisProperties.setClassOverrideProperty(TrustAllSSLSocketFactory.class,"axis.socketFactory");
AxisProperties.setClassDefault(TrustAllSSLSocketFactory.class,"org.apache.axis.components.net.DefaultSocketFactory");
AxisProperties.setClassOverrideProperty(TrustAllSSLSocketFactory.class,"axis.socketSecureFactory");
AxisProperties.setClassDefault(TrustAllSSLSocketFactory.class,"org.apache.axis.components.net.JSSESocketFactory");
AxisProperties.setProperty("org.apache.axis.components.net.SecureSocketFactory", TrustAllSSLSocketFactory.class.getName());

    • Other solution is to use SunJSSESocketFactory by  setting following properties:

AxisProperties.setClassOverrideProperty(SunJSSESocketFactory.class,"axis.socketFactory"); AxisProperties.setClassDefault(SunJSSESocketFactory.class,"org.apache.axis.components.net.DefaultSocketFactory"); AxisProperties.setClassOverrideProperty(SunJSSESocketFactory.class,"axis.socketSecureFactory"); AxisProperties.setClassDefault(SunJSSESocketFactory.class,"org.apache.axis.components.net.JSSESocketFactory"); AxisProperties.setProperty("org.apache.axis.components.net.SecureSocketFactory", SunJSSESocketFactory.class.getName()); 

Service service = new Service();
Call call = (Call) service.createCall();
 ....
 Hashtable hashtable = new Hashtable<>(); 
hashtable.put("protocol", "TLSv1.2"); 
hashtable.put("keystore",""); 
MyRequestHandler handler = new MyRequestHandler(); 
handler.setOptions(hashtable); 
call.setClientHandlers(handler, null); 
 ... 

class MyRequestHandler extends HTTPSender{ 


 @Override 

 public void setOptions(Hashtable opts) {
 Hashtable t = super.getOptions(); 
 for(Srting t : opts)

 t.put("key", "value"); 
 } 
super.setOptions(t); 
 }
 }




Comments

  1. Great Post

    This Resolved my problem also, i was struggling long time

    ReplyDelete
    Replies
    1. Thank you @Satveer. Nice to hear back from you.

      Delete
  2. Hi All

    I have tried the above code change in application side but still i am getting exception saying that "java.io.IOException: TSLv1.1 SSLContext not available". I tried with 1.2 as well as 1.1, i am getting same error.

    Is there any way to get out of this exception. Please suggest

    Thanks,
    Anupam

    ReplyDelete
  3. Hi All

    I have tried the above code change in application side but still i am getting exception saying that "java.io.IOException: TSLv1.1 SSLContext not available". I tried with 1.2 as well as 1.1, i am getting same error.

    Is there any way to get out of this exception. Please suggest

    Thanks,
    Anupam

    ReplyDelete
  4. Great post. This solved the problem we were facing with outbound SSL connections of Axis1.4 frame work from weblogic 10.3.6 server. we went with the "TrustAllSSLSocketFactory" solution.
    Once this code gets initialized during an Axis outbound call, it applies to all future Axis connections,which is good. we didn't need to change all outbound Axis calls. put this code in a static block and invoked a web service cal after that. then all looked good.


    One small typo in the code though :)

    SSLContext context = SSLContext.getInstance("TSLv1.2");

    should be:

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

    ReplyDelete
  5. TrustAllSSLSocketFactory is not working for me .i am getting SocketException:connection reset

    ReplyDelete
  6. I have tried above enforcing TLSv1.2 approach on AXIS client and it worked. Thank you.

    ReplyDelete

Post a Comment

Popular posts

Spring MongoDB Rename field with derived Value of another field

Input Collection -  [ { 'k' : 'Troubleshooting' , 'hour' : '2024-10-10T16' , 'v' : [ 'WebPage, Login' ] }, { 'k' : 'TroubleshootingMe' , 'hour' : '2024-10-07T01' , 'v' : [ 'Accounts, etc' ] }  ] Expected Output -  [ { 'hour' : '2024-10-10T16' , 'Troubleshooting' : [ 'WebPage, Login' ] }, { 'hour' : '2024-10-07T01' , 'TroubleshootingMe' : [ 'Accounts, etc' ] }  ]   Above Can be achieved by  $replaceRoot / $replaceWith as follows - { $replaceWith : { $mergeObjects : [ { hour : "$hour" }, { "$arrayToObject" : [ [ { k : "$k" , v : "$v" } ] ] } ] } } or { $replaceRoo...




What is Leadership

 




Spark Error - missing part 0 of the schema, 2 parts are expected

 Exception -  Caused by: org.apache.spark.sql.AnalysisException : Could not read schema from the hive metastore because it is corrupted. (missing part 0 of the schema, 2 parts are expected).; Analysis -  ·          Check for table definition. In TBLProperties, you might find something like this – > spark.sql.sources.schema.numPartCols > 'spark.sql.sources.schema.numParts' 'spark.sql.sources.schema.part.0' > 'spark.sql.sources.schema.part.1' 'spark.sql.sources.schema.part.2' > 'spark.sql.sources.schema.partCol.0' > 'spark.sql.sources.schema.partCol.1' That’s what error seems to say that part1 is defined but part0 is missing.  Solution -  Drop & re-create table. If Table was partitioned  then all partitions  would have been removed. So do either of below -  ·          Msck repair table <db_name>.<table_name> ·    ...




Spark MongoDB Connector Not leading to correct count or data while reading

  We are using Scala 2.11 , Spark 2.4 and Spark MongoDB Connector 2.4.4 Use Case 1 - We wanted to read a Shareded Mongo Collection and copy its data to another Mongo Collection. We noticed that after Spark Job successful completion. Output MongoDB did not had many records. Use Case 2 -  We read a MongoDB collection and doing count on dataframe lead to different count on each execution. Analysis,  We realized that MongoDB Spark Connector is missing data on bulk read as a dataframe. We tried various partitioner, listed on page -  https://www.mongodb.com/docs/spark-connector/v2.4/configuration/  But, none of them worked for us. Finally, we tried  MongoShardedPartitioner  this lead to constant count on each execution. But, it was greater than the actual count of records on the collection. This seems to be limitation with MongoDB Spark Connector. But,  MongoShardedPartitioner  seemed closest possible solution to this kind of situation. But, it per...




Read from a hive table and write back to it using spark sql

In context to Spark 2.2 - if we read from an hive table and write to same, we get following exception- scala > dy . write . mode ( "overwrite" ). insertInto ( "incremental.test2" ) org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; 1. This error means that our process is reading from same table and writing to same table. 2. Normally, this should work as process writes to directory .hiveStaging... 3. This error occurs in case of saveAsTable method, as it overwrites entire table instead of individual partitions. 4. This error should not occur with insertInto method, as it overwrites partitions not the table. 5. A reason why this happening is because Hive table has following Spark TBLProperties in its definition. This problem will solve for insertInto met...