accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1027) Consolidate the thrift objects for Authentication information
Date Sun, 03 Feb 2013 01:42:13 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569687#comment-13569687
] 

John Vines commented on ACCUMULO-1027:
--------------------------------------

I am working on a fair amount of the client side reversions from 259, and one of them is creating
a new AuthInfo like token, which has identical field types, but more descriptive naming aboard.
This should address any sort of thrift consolidation.
                
> Consolidate the thrift objects for Authentication information
> -------------------------------------------------------------
>
>                 Key: ACCUMULO-1027
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1027
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: master, tserver
>            Reporter: Christopher Tubbs
>            Assignee: John Vines
>             Fix For: 1.5.0
>
>
> Rather than add a new thrift object for each possible type of authentication token (I
saw 3 created for ACCUMULO-259), we should just make our token interface extend Writable,
and use a single thrift object to carry the user principal, token type, and binary serialized
token, in our RPC calls.
> I think the now deprecated "AuthInfo" object was acceptable for this purpose, though
with different fields and behavior than before. However, since that object was in the public
API in 1.4.x, it needs to remain as is, until it is phased out of the public API. A similar
object, (perhaps 'Authentication'), containing the user principal, token type, and binary
serialized token, should be created for this purpose instead, for the RPC calls.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message