[jira] [Commented] (IMPALA-11404) When impalad enables kerberos service , impala-shell failed to access it

["Wenzhe Zhou (Jira)" <ji...@apache.org>]

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

Wenzhe Zhou commented on IMPALA-11404:
--------------------------------------

When using impala-shell with Kerberos, it is assumed that the host has a preexisting kinit-cached Kerberos ticket that impala-shell can pass to the server automatically.
You have to run kinit first, then start the impala-shell with protocol as hs2 and -k option .

Impala 4.0.0 support Kerberos over hs2 for impala-shell.
We recently support Kerberos over hs2-http for impala-shell.

> When impalad enables kerberos service , impala-shell failed to access it
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-11404
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11404
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Clients
>    Affects Versions: Impala 4.0.0
>            Reporter: Davy Xu
>            Priority: Major
>
> When running the impala service with kerberos enabled on SUSE12 system, impala-shell fails to access impalad, and the error message is as follows:
> Error connecting: TTransportException, Could not start SASL: Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (No Kerberos credentials available)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org