Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8234810163 for ; Wed, 23 Oct 2013 20:27:56 +0000 (UTC) Received: (qmail 12033 invoked by uid 500); 23 Oct 2013 20:27:47 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 11989 invoked by uid 500); 23 Oct 2013 20:27:44 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 11967 invoked by uid 99); 23 Oct 2013 20:27:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Oct 2013 20:27:42 +0000 Date: Wed, 23 Oct 2013 20:27:42 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803283#comment-13803283 ] stack commented on HBASE-9221: ------------------------------ Patch looks good. Any danger of this being the default; i.e. a new Connection each time? + * @param ticket Be careful which ticket you pass. A new user will mean a new Connection. + * {@link UserProvider#getCurrent()} makes a new instance of User each time so will be a + * new Connection each time. Is that just a module move for the User class? Is the remove of hbase-protocol/src/main/protobuf/HBase.proto intended? Else patch lgtm. > Provide interface for getting a User in the client > -------------------------------------------------- > > Key: HBASE-9221 > URL: https://issues.apache.org/jira/browse/HBASE-9221 > Project: HBase > Issue Type: Improvement > Components: Client, hadoop2, security > Affects Versions: 0.98.0, 0.95.2, 0.94.12 > Reporter: Jesse Yates > Assignee: Jesse Yates > Fix For: 0.98.0, 0.94.13, 0.96.1 > > Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch > > > Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. > This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)