Feedback
Did this article resolve your question/issue?

   

Article

What key and trust store formats are supported by the Connect for ODBC 7.1 drivers that support SSL?

Information

 
TitleWhat key and trust store formats are supported by the Connect for ODBC 7.1 drivers that support SSL?
URL Name000053856
Article Number000170333
EnvironmentProduct: Connect for ODBC drivers that support SSL
Version: 7.1
OS: All supported platforms
Database: DB2, Greenplum, MySQL, Oracle, PostgreSQL, Progress OpenEdge, SQL Server, Sybase
Application: All applications
Question/Problem Description
What key and trust store formats are supported by the Connect for ODBC 7.1 drivers that support SSL?
Steps to Reproduce
Clarifying Information
The following ODBC 7.1 drivers support SSL:
  • Apache Hive Wire Protocol
  • DB2 Wire Protocol
  • Greenplum Wire Protocol
  • Impala Wire Protocol
  • MySQL Wire Protocol
  • Oracle Wire Protocol
  • PostgreSQL Wire Protocol
  • Progress OpenEdge Wire Protocol
  • Salesforce
  • SQL Server Wire Protocol
  • Sybase Wire Protocol
Error Message
Defect Number
Enhancement Number
Cause
Resolution
The Connect for ODBC 7.1 drivers that support SSL support the following truststore formats:
- DER Encoded Binary X.509
- Base64 Encoded X.509
- PKCS #12 / Personal Information Exchange
- PKCS #7 
- PEM

When using a keystore, the drivers support the following formats:
- Base64 Encoded X.509
- PKCS #12 / Personal Information Exchange
- PKCS #7 
- PEM
Workaround
Notes
Last Modified Date3/12/2021 7: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.