You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nicolas Liochon (JIRA)" <ji...@apache.org> on 2015/10/08 15:49:27 UTC

[jira] [Created] (HBASE-14580) Make the HBaseMiniCluster compliant with Kerberos

Nicolas Liochon created HBASE-14580:
---------------------------------------

             Summary: 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


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/localhost@EXAMPLE.COM.hfs.0, 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)