[
https://issues.apache.org/jira/browse/HBASE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446110#comment-13446110
]
Gary Helmling commented on HBASE-6699:
--------------------------------------
So, after the header is written, the magic invocation is passed to set the
username? That seems a little ugly. Seems like it would be simpler to just
change ConnectionHeader to actually handle User (all the bit's are there, it
just always uses "null"), though that would change the serialization of
ConnectionHeader and not be back-compatible, so maybe that's out.
Getting back to the original issue, if the need is just to have username
present without kerberos auth, couldn't you just use SecureRpcEngine with
hbase.security.authentication set to "simple"? Then you would get usernames
passed through for each connection, just without kerberos auth.
> 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.3, 0.94.2
>
> Attachments: HBase-6699-v1.patch
>
>
> 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
