[jira] [Commented] (CALCITE-1214) Support url-based kerberos login

["Josh Elser (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261025#comment-15261025 ] 

Josh Elser commented on CALCITE-1214:
-------------------------------------

One thing I also ran into while making this change is that we were actually instantiating two instances of the RemoteService in Driver: in {{createMeta}} and then again in {{connect(..)}}.

I would think that it makes sense to tie the Service to the AvaticaConnection (thus the resources of the Service would be tied to the lifetime of the Connection).

> 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)