[
https://issues.apache.org/jira/browse/CALCITE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262676#comment-15262676
]
Josh Elser commented on CALCITE-1214:
-------------------------------------
bq. 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.
Good point. It was once a static class without state. Will modify. Thanks for
looking!
> 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)
