[
https://issues.apache.org/jira/browse/SQOOP-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259593#comment-14259593
]
Abraham Elmahrek commented on SQOOP-1776:
-----------------------------------------
I'd just like to note the way I tested this feature (fetching a delegation
token) was by using the following:
{code}
curl --negotiate -u :
http://<host>:<port>/sqoop/v1/?op=GETDELEGATIONTOKEN&renew=<user>
{code}
Ref: http://hadoop.apache.org/docs/r1.0.4/webhdfs.html#GETDELEGATIONTOKEN
> Sqoop2: Delegation Token support for Authentication
> ---------------------------------------------------
>
> Key: SQOOP-1776
> URL: https://issues.apache.org/jira/browse/SQOOP-1776
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-framework
> Reporter: Richard
> Assignee: Richard
> Fix For: 1.99.5
>
> Attachments: SQOOP-1766-v5.patch, SQOOP-1776-v6.patch
>
>
> Hadoop 2.5.1 or before: all classes used to implement Kerberos support is in
> Hadoop-auth component.
> Hadoop 2.6.0: There is a refactor to support delegation token in Hadoop [4].
> Most components in Hadoop, such as RM, Httpfs and Kms, have rewritten
> authentication mechanism to use delegation token.
> https://issues.apache.org/jira/browse/HADOOP-10771
> So, this task is to refactor authentication mechanism to support delegation
> token.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
