[
https://issues.apache.org/jira/browse/DRILL-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803154#comment-15803154
]
ASF GitHub Bot commented on DRILL-4280:
---------------------------------------
Github user sohami commented on a diff in the pull request:
https://github.com/apache/drill/pull/578#discussion_r94866946
--- Diff:
exec/java-exec/src/test/java/org/apache/drill/exec/server/TestOptionsAuthEnabled.java
---
@@ -17,7 +17,10 @@
*/
package org.apache.drill.exec.server;
+import com.google.common.collect.Lists;
+import com.typesafe.config.ConfigValueFactory;
import org.apache.drill.BaseTestQuery;
+import org.apache.drill.common.config.ConnectionParameters;
import org.apache.drill.common.config.DrillConfig;
--- End diff --
It would be great to add negative. Some of which I can think of are as
below. Not sure if they are already covered.
1) Server not configured for any mechanism.
2) Server configured for mechanism but client requesting some other
mechanism for authentication
3) Client getting service ticket for one host but sending message to
different host.
4) Client trying to authenticate with kdc using wrong creds.
> Kerberos Authentication
> -----------------------
>
> Key: DRILL-4280
> URL: https://issues.apache.org/jira/browse/DRILL-4280
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Keys Botzum
> Assignee: Sudheesh Katkam
> Labels: security
>
> Drill should support Kerberos based authentication from clients. This means
> that both the ODBC and JDBC drivers as well as the web/REST interfaces should
> support inbound Kerberos. For Web this would most likely be SPNEGO while for
> ODBC and JDBC this will be more generic Kerberos.
> Since Hive and much of Hadoop supports Kerberos there is a potential for a
> lot of reuse of ideas if not implementation.
> Note that this is related to but not the same as
> https://issues.apache.org/jira/browse/DRILL-3584
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
