accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1028) Distinguish the user principal from the authentication token
Date Sun, 03 Feb 2013 20:14:12 GMT


Christopher Tubbs commented on ACCUMULO-1028:

Agreed. I just don't know how that relates to this ticket, which is about the API, not serialization.
I made another ticket that relates more to serialization (ACCUMULO-1027), to support a wider
variety of tokens by only requiring them to know how to convert to a binary to be carried
in a thrift object, and Eric made a ticket (ACCUMULO-1003) to question the API that determines
the method by which tokens are actually serialized.

Is there a way I can re-word this ticket, to make it more clear that it's about the API?
> Distinguish the user principal from the authentication token
> ------------------------------------------------------------
>                 Key: ACCUMULO-1028
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: master, tserver
>            Reporter: Christopher Tubbs
>             Fix For: 1.5.0
> The user principal is something that uniquely identifies a user. An authentication token
is the item that authenticates the user principal, may be temporal, and may vary. It is not
clear from the implementation of ACCUMULO-259 that these are separate things, and I think
it would benefit the API to distinguish them.
> It could also simplify the API, for users transitioning from the old authentication stuff
to the new authentication stuff, because there would be a one-to-one mapping with the username/password
with which they are familiar:
> {code:java}
> public Connector getConnector(String username, byte[] password);
> {code}
> becomes
> {code:java}
> public <T extends AuthToken> Connector getConnector(Principal userPrincipal, T
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message