Feedback
Did this article resolve your question/issue?

   

Article

Is there a way to specify a particular Kerberos ticket cache to use in odbc datasource

Information

 
TitleIs there a way to specify a particular Kerberos ticket cache to use in odbc datasource
URL Nameis-there-a-way-to-specify-a-particular-kerberos-ticket-cache-to-use-in-odbc-datasource
Article Number000175836
EnvironmentProduct : Connect for ODBC Apache Hive Wire Protocol driver
Version : 7.10.06.368
Database : Apache Hive
OS : All supported platforms
Application : All supported applications
Question/Problem Description
Is there a way to specify a particular Kerberos ticket cache to use in odbc datasource.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Kerberos ticket cache can not be set via the ODBC driver configuration however this can be configured using an environment variable or within the kerberos conf file.

The Mit Kerberos GSS docs should have more details regarding this;

Can be configured in the krb5.conf (or .ini) file 
default_ccache_name = FILE:/tmp/krb5cache 

Using environment variable:
setenv KRB5CCNAME FILE: /tmp/krb5cache 
Workaround
Notes
Last Modified Date11/1/2016 8:21 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.