Feedback
Did this article resolve your question/issue?

   

Article

Can't make an SSL ODBC database connection with a trust store built using Java keytool

Information

 
TitleCan't make an SSL ODBC database connection with a trust store built using Java keytool
URL NameCan-t-make-an-SSL-ODBC-database-connection-with-a-trust-store-built-using-Java-keytool
Article Number000120038
EnvironmentProduct: Connect for ODBC all drivers
Version: All supported versions
OS: All support platforms
Database: All supported databases
Application: All supported applications
Question/Problem Description
Can't make an SSL ODBC database connection using DataDirect Connect for ODBC drivers with a trust store built using the Java keytool utility.
Steps to Reproduce
Clarifying Information
The trust store was built using Java keytool with the "-importcert" parameter.
Error Message
Defect Number
Enhancement Number
Cause
When the parameter -importcert is used, the DataDirect ODBC drivers are not going to be able to read the file due to that fact that keytool uses the JKS file format by default and the OpenSSL library used by the driver is not able to read the JKS format. 
 
Resolution
It's possible to instruct keytool to create the keystore using PKCS12 format and then OpenSSL will be able to read the keystore. 
Build the trust store using the following command: 
keytool.exe -importcert -v -storetype pkcs12 -file C:\<path>\mycert.cer -keystore myks.jks -storepass mypwd 
 
Workaround
Notes
Last Modified Date3/28/2019 2:50 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.