Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 31 Aug 2012 16:41:07 +1100 (NCT)
From: "Himanshu Vashishtha (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1647769021.20890.1346391667729.JavaMail.jiratomcat@arcas>
In-Reply-To: <1303819287.20875.1346391308525.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6699) Setting username in Connection in
 non-secure HBase
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Himanshu Vashishtha commented on HBASE-6699:
--------------------------------------------

Here are the two approaches:
1) Change the ConnectionHeader so that it *actually* sets the User object, rather than just providing stubs to do so. This will change the Writable and then we need to do version number jugglery for compatibility.
2) Make a *pesudo call* to a non-existent method while creating the connection, and let the new server handle it by setting the connection.ticket to the requester. (Credit to Todd for this suggestion)

Attached is a patch with the second approach. I tested it with patched server versus unpatched client, and vice versa.
                
> Setting username in Connection in non-secure HBase
> --------------------------------------------------
>
>                 Key: HBASE-6699
>                 URL: https://issues.apache.org/jira/browse/HBASE-6699
>             Project: HBase
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.92.0, 0.92.1, 0.94.0, 0.94.1
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>             Fix For: 0.92.2, 0.94.2
>
>
> We recently had a requirement where we need to log the information about various users who were using non-secure HBase cluster. 
> The user level logging is supported as part of security, but in 0.92, 0.94 security related code is separate. This jira is about adding that support in non-secure code.
> This feature is already there in trunk, after we merge the security related code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira