[
https://issues.apache.org/jira/browse/HBASE-14580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032138#comment-15032138
]
Nick Dimiduk commented on HBASE-14580:
--------------------------------------
Sorry I missed the earlier poke.
We have thus far not considered APIs and behaviors in our test jars as falling
under the guidelines of our semantic version efforts (see PerfEval, for
instance). Thus I think this should be acceptable for 1.0.x and 1.1.x.
> Make the HBaseMiniCluster compliant with Kerberos
> -------------------------------------------------
>
> Key: HBASE-14580
> URL: https://issues.apache.org/jira/browse/HBASE-14580
> Project: HBase
> Issue Type: Improvement
> Components: security, test
> Affects Versions: 2.0.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 2.0.0, 1.3.0, 1.2.1, 0.98.16
>
> Attachments: hbase-14580.v2.patch, hbase-14580.v2.patch,
> patch-14580.v1.patch
>
>
> Whne using MiniKDC and the minicluster in a unit test, there is a conflict
> causeed by HBaseTestingUtility:
> {code}
> public static User getDifferentUser(final Configuration c,
> final String differentiatingSuffix)
> throws IOException {
> // snip
> String username = User.getCurrent().getName() +
> differentiatingSuffix; <==================== problem here
> User user = User.createUserForTesting(c, username,
> new String[]{"supergroup"});
> return user;
> }
> {code}
> This creates users like securedUser/[email protected], and this
> does not work.
> My fix is to return the current user when Kerberos is set. I don't think that
> there is another option (any other opinion?). However this user is not in a
> group so we have logs like 'WARN [IPC Server handler 9 on 61366]
> security.UserGroupInformation (UserGroupInformation.java:getGroupNames(1521))
> - No groups available for user securedUser' I'm not sure of its impact.
> [~apurtell], what do you think?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
