[ https://issues.apache.org/jira/browse/HBASE-20886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564183#comment-16564183 ]
Josh Elser commented on HBASE-20886: ------------------------------------ [~reidchan] sorry for the delay! Your v8 patch looks OK. I think the only concern I have (not sure if it's legitimate, either) is over MapReduce. I don't know if we have any MapReduce tests with Kerberos turned on. Assuming not, did you try out this new feature when running a M/R job? > [Auth] Support keytab login in hbase client > ------------------------------------------- > > Key: HBASE-20886 > URL: https://issues.apache.org/jira/browse/HBASE-20886 > Project: HBase > Issue Type: New Feature > Components: asyncclient, Client, security > Reporter: Reid Chan > Assignee: Reid Chan > Priority: Critical > Fix For: 3.0.0, 2.2.0 > > Attachments: HBASE-20886.master.001.patch, > HBASE-20886.master.002.patch, HBASE-20886.master.003.patch, > HBASE-20886.master.004.patch, HBASE-20886.master.005.patch, > HBASE-20886.master.006.patch, HBASE-20886.master.007.patch, > HBASE-20886.master.008.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)