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

Reid Chan commented on HBASE-20886:
-----------------------------------

Those two options are already existed in code base. The canary implementation 
is a legacy, and client principal doesn't have to have hostname, so i add a new 
one.
BTW, where are these configurations 
{{hadoop.property.hadoop.client.keytab.file}}, 
{{hadoop.property.hadoop.client.kerberos.principal}}. I'm afraid i have missed 
them..

> [Auth] Support keytab login in hbase client
> -------------------------------------------
>
>                 Key: HBASE-20886
>                 URL: https://issues.apache.org/jira/browse/HBASE-20886
>             Project: HBase
>          Issue Type: Improvement
>          Components: asyncclient, Client, security
>            Reporter: Reid Chan
>            Assignee: Reid Chan
>            Priority: Critical
>         Attachments: HBASE-20886.master.001.patch
>
>
> There're lots of questions about how to connect to kerberized hbase cluster 
> through hbase-client api from user-mail and slack channel.
> {{hbase.client.keytab.file}} and {{hbase.client.keytab.principal}} are 
> already existed in code base, but they are only used in {{Canary}}.
> This issue is to make use of two configs to support client-side keytab based 
> login, after this issue resolved, hbase-client should directly connect to 
> kerberized cluster without changing any code as long as 
> {{hbase.client.keytab.file}} and {{hbase.client.keytab.principal}} are 
> specified.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to