Feedback
Did this article resolve your question/issue?

   

Article

Configure credential cache file in the Oracle ODBC driver

Information

 
TitleConfigure credential cache file in the Oracle ODBC driver
URL Nameconfigure-credential-cache-file-in-the-oracle-odbc-driver
Article Number000178554
EnvironmentProduct : Connect for ODBC Oracle Wire Protocol driver
Version : All supported versions
Database : Oracle
OS : All supported platforms
Application : All supported applications
Question/Problem Description
Is it possible to configure credential cache file in the ODBC driver ?
Steps to Reproduce
Clarifying Information
When the application needs to communicate with different database systems the requirement is to use multiple users in a single process. For example source is Database1 and target is Database2. User A has permissions on Database1 and user B has permissions on Database2. So in a single process, 2 different users should be used.
Error Message
Defect Number
Enhancement Number
Cause
Resolution
This is not possible. The C interface, GSSAPI, always uses a ticket cache which can contain only one set of credentials. Kinit can get the credentials from a keytab that has multiple credentials, but it will only get one of them. 
Workaround
Notes
Last Modified Date11/9/2016 1:36 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.