[
https://issues.apache.org/jira/browse/CALCITE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262669#comment-15262669
]
Julian Hyde edited comment on CALCITE-1214 at 4/28/16 6:24 PM:
---------------------------------------------------------------
Review comments:
* I think you need to rename KerberosUtility. Utilities don't have state,
whereas KerberosUtility has mutable state and presumably thread-safety issues
if it is used wrongly. KerberosConnection might be more fitting.
* How do you know that renewal threads get closed? Should Avatica be using an
execution service for this kind of stuff, so we can use a small thread pool for
everything?
was (Author: julianhyde):
I think you need to rename KerberosUtility. Utilities don't have state, whereas
KerberosUtility has mutable state and presumably thread-safety issues if it is
used wrongly. KerberosConnection might be more fitting.
> Support url-based kerberos login
> --------------------------------
>
> Key: CALCITE-1214
> URL: https://issues.apache.org/jira/browse/CALCITE-1214
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: avatica-1.8.0
>
>
> I was talking with someone today about JDBC drivers in BI-tools/app-servers
> which reminded me about the general guidance to "make your driver work with a
> jar and a JDBC url".
> With the work I added recently to support client authentication with
> Kerberos, I wrote it under the expectation that clients are already logged in
> via a ticket cache (and have the appropriate system properties or environment
> variables set to point at the ticket cache). This doesn't jive with the
> original "jar and url" notion.
> It should be pretty easy to support a principal and keytab property to enable
> these types of environments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
