You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/02/08 00:21:00 UTC
[jira] [Commented] (IMPALA-9367) Allow specifying MEMORY kerberos
credential cache
[ https://issues.apache.org/jira/browse/IMPALA-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032764#comment-17032764 ]
Tim Armstrong commented on IMPALA-9367:
---------------------------------------
This may not actually be possible, because the Java side of Impala shares a ticket cache with the C++ side, but it doesn't look like the Java implementation of kerberos supports the same in-memory credential cache.
> Allow specifying MEMORY kerberos credential cache
> -------------------------------------------------
>
> Key: IMPALA-9367
> URL: https://issues.apache.org/jira/browse/IMPALA-9367
> Project: IMPALA
> Issue Type: Improvement
> Components: Security
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: kerberos
>
> Currently --krb5_ccname defaults to "/tmp/krb5cc_impala_internal" and requires that the argument be an absolute path.
> Kudu actually defaults to "MEMORY:kudu" as its credential cache, which may have some advantages, e.g. it doesn't depend on the filesystem.
> It would be reasonable to allow setting the credential cache type to MEMORY.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org