You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/03/10 23:20:38 UTC

[jira] [Resolved] (ACCUMULO-3599) Get more (all) ITs running with Kerberos

     [ https://issues.apache.org/jira/browse/ACCUMULO-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved ACCUMULO-3599.
----------------------------------
    Resolution: Fixed

We should have the cartesian product of unsecure/secure and minicluster/standalone cluster working. Founds some nice bugs against 1.7.0 along the way. It's probable that I broke some extra tests along the way, but, to the best of my knowledge, I have not.

> Get more (all) ITs running with Kerberos
> ----------------------------------------
>
>                 Key: ACCUMULO-3599
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3599
>             Project: Accumulo
>          Issue Type: Test
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> As a part of ACCUMULO-2815 and ACCUMULO-3513, a KerberosIT was added that work, although there is no way to run the existing IT suite against a secure cluster.
> It would be ideal to be able to run all tests against an Accumulo cluster using Kerberos, even better would be the ability to have a {{-DuseKerberosForITs}} flag like SSL.
> The big change will be the management of users as PasswordTokens will no longer be valid. Creating and using keytabs for test users isn't an issue, but avoiding rewriting every test with a conditional block might be tricky since we currently have no use of {{UserGroupInformation}} in our normal tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)