accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3424) Token class option always requires token property
Date Tue, 16 Dec 2014 20:04:13 GMT


Josh Elser commented on ACCUMULO-3424:

Looking at the history, it looks like some changes were made in ACCUMULO-1323 and maybe were
misintepreted in ACCUMULO-1478? I can't see a reason for enforcing that we always have token
properties from the initial change. If anyone has more context, please let me know.

> Token class option always requires token property
> -------------------------------------------------
>                 Key: ACCUMULO-3424
>                 URL:
>             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
> 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}}
 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
-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

View raw message