Feedback
Did this article resolve your question/issue?

   

Article

How to configure the JVM to use specific TLS versions when connecting with Connect for ODBC Oracle Service Cloud driver

Information

 
TitleHow to configure the JVM to use specific TLS versions when connecting with Connect for ODBC Oracle Service Cloud driver
URL Namehow-to-configure-the-jvm-to-use-specific-tls-versions-when-connecting-with-connect-for-odbc-oracle-service-cloud-driver
Article Number000183379
EnvironmentDataDirect-DataDirect for ODBC Orac *le Service Cloud 64-bit-Windows-Windows 2012 standard
Question/Problem Description
How to configure the JVM to use specific TLS versions when connecting with Connect for ODBC Oracle Service Cloud driver.  

Oracle Service Cloud no longer supports TLSv1.0; however, some JVM versions default to TLSv1.0.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
If using a JVM that is older than version 1.8, it may be necessary to configure the JVM to use a specific set of TLS versions.

To configure the JVM via the Connect for ODBC Oracle Service Cloud driver, modify the JVMArgs connect option to include the following JVM argument:

-Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2

For example:

JVMArgs={-Xmx256m -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2} 

Note the space delimited JVM arguments enclosed in curly brackets.  More details can be found in the Driver User's Guide.
Workaround
Notes
Last Modified Date1/27/2017 10:12 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.