Project

General

Profile

Task #7131

Bug #7058: cannot successfully connect to SAEON node that only uses TLSv1.2

implement a TLS protocol preference property in auth.properties

Added by Rob Nahf over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_libclient_java
Target version:
-
Start date:
2015-05-26
Due date:
% Done:

100%

Estimated time:
0.00 h
Story Points:
Sprint:

Description

Allow the user to configure a preference of TLS protocols to use, via a property called tls.protocol.preferences
in auth.properties.
Certificate manage will iterate over the list until it finds a protocol the runtime supports. This lets us specify the
highest version of TLS we wish without worrying about what a particular runtime supports.

The preference list will allow libclient run under java 6 use TLSv1.0 (the highest it supports), under java7 and 8 use TLSv1.2.


Subtasks

Task #7132: implement protocol preference in d1_libclient_java v1.4 branch ClosedRob Nahf

Task #7133: implement protocol preference in d1_libclient_java v2.0 (trunk)ClosedRob Nahf

History

#1 Updated by Rob Nahf over 9 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 30 to 100

#2 Updated by Rob Nahf over 9 years ago

added the tls.protocol.preferences property to CertificateManager to give maximum runtime compatibility and security for TLS connections. Default preferences support java 6,7, & 8 at their highest supported protocol version.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)