You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by Stack <st...@duboce.net> on 2013/04/19 03:22:50 UTC

Is it correct that TokenInfo is always "HBASE_AUTH_TOKEN"?

All Interfaces seem to have same @TokenInfo.  In my naivety, I'd think that
AdminProtocol would have HBASE_AUTH_TOKEN but say ClientProtocol would have
HBASE_CLIENT_TOKEN?  Do I have it wrong?

Thanks,
St.Ack

Re: Is it correct that TokenInfo is always "HBASE_AUTH_TOKEN"?

Posted by Stack <st...@duboce.net>.

Thanks boss.
St.Ack


On Thu, Apr 18, 2013 at 7:12 PM, Gary Helmling <gh...@gmail.com> wrote:

> Yes its always HBASE_AUTH_TOKEN.  This corresponds to the type set when the
> token is granted and we only grant one type.  I don't think it makes sense
> to split into this into 2 types and have to always grant and store 2
> separate tokens.
>
> I'm going through the 8214 patch as well.  Sorry to be slow in feedback.
> On Apr 18, 2013 6:23 PM, "Stack" <st...@duboce.net> wrote:
>
> > All Interfaces seem to have same @TokenInfo.  In my naivety, I'd think
> that
> > AdminProtocol would have HBASE_AUTH_TOKEN but say ClientProtocol would
> have
> > HBASE_CLIENT_TOKEN?  Do I have it wrong?
> >
> > Thanks,
> > St.Ack
> >
>

Re: Is it correct that TokenInfo is always "HBASE_AUTH_TOKEN"?

Posted by Gary Helmling <gh...@gmail.com>.

Yes its always HBASE_AUTH_TOKEN.  This corresponds to the type set when the
token is granted and we only grant one type.  I don't think it makes sense
to split into this into 2 types and have to always grant and store 2
separate tokens.

I'm going through the 8214 patch as well.  Sorry to be slow in feedback.
On Apr 18, 2013 6:23 PM, "Stack" <st...@duboce.net> wrote:

> All Interfaces seem to have same @TokenInfo.  In my naivety, I'd think that
> AdminProtocol would have HBASE_AUTH_TOKEN but say ClientProtocol would have
> HBASE_CLIENT_TOKEN?  Do I have it wrong?
>
> Thanks,
> St.Ack
>