Skip to Main Content

Java Database Connectivity (JDBC)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

TLSv1.2 with Thin JDBC driver

User_5FQQHNov 4 2015 — edited Nov 10 2015

I've set up a secure connection, and the handshake connects using TLSv1.

Is there a way to have it negotiate TLSv1.2?

I'm using ojdbc7.jar from 12.1.0.2

The connection is made using a javax.sql.DataSource reference with org.apache.commons.dbcp.BasicDataSourceFactory

The secure connection works, and it negotiates a TLSv1 connection. However, I've been asked to use TLSv1.2. The client initiates the handshake with:

"*** ClientHello, TLSv1"

Which means the server will negotiate back with TLSv1.

How do I get the client to start the handshake with a hello TLSv1.2?

I've tried setting the following options:

-Djdk.tls.client.protocols=TLSv1.2

-Dhttps.protocols=TLSv1.2

but neither has had an effect.

This post has been answered by User_5FQQH on Nov 10 2015
Jump to Answer

Comments

4297041
Answer
Hello EssbaseApprentice,

Any product that is either installed/configured/deployed via the EPM Configurator AFTER Workspace has been deployed will not be reflected inside of Workspace. This is becaues the Workspace configuration stores static content in an .XML file of the Application tier and is not dynamically driven. You will need to redeply Workspace to have all changes reflected and demonstrated.

Also you can not go directly to most products starting in v11.1.1.3.00 as they will require the SharedServices SSO token to process as most products will not have a direct logon page going into the future. Workspace will be a requirement.

Thank you,
Marked as Answer by essapp · Sep 27 2020
essapp
Thanks, I marked it as correct.
1 - 2
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Dec 8 2015
Added on Nov 4 2015
6 comments
6,794 views