[
https://issues.apache.org/jira/browse/CALCITE-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752313#comment-15752313
]
Jerry He commented on CALCITE-1539:
-----------------------------------
bq. Do you know if Hue works in the same manner?
Yes, AFAIK for HBase case it goes through HBase Thrift server using the doAs.
bq. The trick here in Avatica is that we have to not think in "terms of
Hadoop". That is not in the picture at all.
Yes. Looking at the portion of the code, could we add another API in the
DoAsRemoteUserCallback interface, like
{code}
public <T> T doAsRemoteUser(String remoteUserName, String
remoteEffectiveUserName, String remoteAddress, final Callable<T> action)
{code}
Avatica fills it out and the implementation decides what to do.
I am happy to help out :-). But I may take me a while to get the env to
provide a patch out :-(
> Enable proxy access to Avatica server for third party on behalf of end users
> ----------------------------------------------------------------------------
>
> Key: CALCITE-1539
> URL: https://issues.apache.org/jira/browse/CALCITE-1539
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: Jerry He
> Assignee: Josh Elser
>
> We want to enable proxy access to Avatica server from an end user, but the
> end user comes in via a third party impersonation. For example, Knox and Hue.
> The Knox server user conveys the end user to Avatica.
> Similar things have been done for HBase Rest Sever HBASE-9866 and Hive Server
> HIVE-5155
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
