Feedback
Did this article resolve your question/issue?

   

Article

How to configure the Oracle driver using Kerberos with ticket caches maintained in a shared folder.

Information

 
TitleHow to configure the Oracle driver using Kerberos with ticket caches maintained in a shared folder.
URL NameHow-to-configure-the-Oracle-driver-using-Kerberos-with-ticket-caches-maintained-in-a-shared-folder
Article Number000113133
EnvironmentProduct: Connect for JDBC Oracle driver
Version: 5.1
OS: Java
Database: Oracle
Application: All supported applications
Question/Problem Description
How to configure the Connect for JDBC Oracle driver using Kerberos with ticket caches maintained in a shared folder.
Steps to Reproduce
Clarifying Information
Specifying the ticket cache location in the JAAS config JDBC_DRIVER_01 but that limits that JVM to that ticket cache. Is their a way to use a different AD user with different JDBC pool.
Error Message
Defect Number
Enhancement Number
Cause
Resolution
There is a loginConfigName connect option for just this kind of thing (connections using different ticket caches part not the proxy user part). It defaults to "JDBC_DRIVER_01", but this can be set it to any name on a per-connection basis. Add a configuration for it to the jaas config file that points to a different ticket cache or uses different jaas options.

Note using a proxy user connection is not supported ("OracleConnection.openProxyConnection())". This would be considered a driver enhancement.

For additional information refer to the DataDirect driver documentation.
Workaround
Notes
References to other documentation:
Progress Article(s):
 How to submit an enhancement request for a Progress product?

References to other documentation:
DataDirect Driver Documentation, https://www.progress.com/documentation/datadirect-connectors

 
Last Modified Date11/20/2020 6:56 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.