Project

General

Profile

Story #7060

refactor CertificateManager to specify TLSv1.2 in v1.x branch

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

Status:
Rejected
Priority:
High
Assignee:
Category:
d1_libclient_java
Target version:
Start date:
2015-04-23
Due date:
% Done:

0%

Story Points:
Sprint:

Description

Initial tests against TLS 1.0 - accepting MNs in production (PISCO, Merritt, LTER-EU, and NPN) indicate that setting the protocol to TLSv1.2 does not affect our ability to connect to them.

We will need to include this in the CCI1.5.1 release.

Consider parameterizing the SSL protocol parameter, so package uses are not stuck with our choice.


Related issues

Related to Java Client - Bug #7058: cannot successfully connect to SAEON node that only uses TLSv1.2 Closed 2015-05-26

History

#1 Updated by Rob Nahf over 6 years ago

  • Parent task deleted (#7058)

#2 Updated by Rob Nahf over 6 years ago

  • Tracker changed from Task to Story

#3 Updated by Rob Nahf over 6 years ago

  • Target version set to CLJ-1.4.0

#4 Updated by Rob Nahf over 6 years ago

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

#5 Updated by Rob Nahf over 6 years ago

  • Status changed from New to Rejected

(duplicate)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)