Feedback
Did this article resolve your question/issue?

   

Article

Using signed cipher suites with OpenAccess ODBC client

Information

 
TitleUsing signed cipher suites with OpenAccess ODBC client
URL Name000050154
Article Number000168655
EnvironmentProduct : OpenAccess ODBC Client
Version : All supported versions
Database : NA
OS : All supported platforms
Application : All supported applications
Question/Problem Description
What cipher suite is used when both anonymous and non-anonymous ciphersuites are available on the server and client has truststore property set?  How is the 128 AES encryption initialized in this case?  Is it DH (anonymous) or RSA?
How to use non-anonymous cipher suites with OpenAccess ODBC Client? 
Is it possible for the ODBC client to use system (Windows) Root CA or Intermediate CA without certificate defined by application by truststore property in ODBC client?
Is it possible to specify a non-anonymous cipher suite on the client side?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
  • When the TrustStore property is set at the ODBC client side, a non-anonymous cipher suite (e.g. TLS_RSA_WITH_AES_128_CBC_SHA) will be used for the client and server communication.  
  • The TrustStore property is mandatory for non-anonymous cipher communication.  If the TrustStore property is not specified, an anonymous cipher suite (e.g. TLS_DH_anon_WITH_AES_128_CBC_SHA) will be used.
  • Currently It is not possible to use the (Windows/Linux) root CA or intermediate CA without providing the certificate (TrustStore) by the application.
  • OpenAccess ODBC client does not have any option to set the cipher suite from the client side.
Workaround
Notes
References to other documentation:
OpenAccess SDK Client Reference, Using the ODBC Client, Using SSL Encryption
https://media.datadirect.com/download/docs/openaccess/alloa/index.html#page/clientref%2Fusing-ssl-encryption.html

OpenAccess SDK Client Reference, Using the ODBC Client, Summary: Encryption-Related Attributes
https://media.datadirect.com/download/docs/openaccess/alloa/index.html#page/clientref%2Fsummary-3a-encryption-related-attributes.html

Progress article:
 Supported cipher suites with OpenAccess SDK 8.1
Last Modified Date11/20/2020 7:03 AM
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.