You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/04/29 21:13:13 UTC
[jira] [Resolved] (CALCITE-1214) Support url-based kerberos login
[ https://issues.apache.org/jira/browse/CALCITE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser resolved CALCITE-1214.
---------------------------------
Resolution: Fixed
Committed this in https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=b7fbb35b3883d5bbead0892c6898711253ddac24. Thanks for the review, Julian. If you have more concerns, let me know as always.
> 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)