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 2014/12/16 21:36:14 UTC
[jira] [Resolved] (ACCUMULO-3424) Token class option always
requires token property
[ https://issues.apache.org/jira/browse/ACCUMULO-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser resolved ACCUMULO-3424.
----------------------------------
Resolution: Fixed
> Token class option always requires token property
> -------------------------------------------------
>
> Key: ACCUMULO-3424
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3424
> Project: Accumulo
> Issue Type: Bug
> Components: shell
> Affects Versions: 1.6.0, 1.6.1
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.6.2, 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In testing out ACCUMULO-2815, I attempted to manually provide a KerberosToken to authenticate myself and then launch the shell, but ran into an issue. The KerberosToken (in its current state) needs no options: it's wholly functional on its own.
> {{accumulo shell -tc org.apache.accumulo.core.client.security.tokens.KerberosToken}} gives an error
> {noformat}
> 2014-12-16 11:41:09,712 [shell.Shell] ERROR: com.beust.jcommander.ParameterException: Must supply either both or neither of '--tokenClass' and '--tokenProperty'
> {noformat}
> And providing an empty option just prints the help message {{accumulo shell -tc org.apache.accumulo.core.client.security.tokens.KerberosToken -l ""}}
> I'm guessing the latter is just how the JCommander DynamicParameter is implemented, but I don't see a reason why every authentication *must* have some properties provided to it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)