[
https://issues.apache.org/jira/browse/HCATALOG-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099594#comment-13099594
]
Sushanth Sowmyan commented on HCATALOG-94:
------------------------------------------
As worded, closely related to HCATALOG-69.
As currently implemented, we mimic the hive delegation token mechanics, and we
do use the token the client provides if they provide it(oozie semantics), and
don't talk to the JT in that case. So if the intent of this jira is that we
should not talk to the JobTracker to get the delegation token at all if not
already specified by the caller, then I'm not convinced.
But, as described to me, there is another issue here, and that of fetching the
JT token in cases where we don't use har, and that needs to be fixed if it
exists.
> Handle the job tracker tokens properly in har jobs
> --------------------------------------------------
>
> Key: HCATALOG-94
> URL: https://issues.apache.org/jira/browse/HCATALOG-94
> Project: HCatalog
> Issue Type: Bug
> Components: security
> Affects Versions: 0.2
> Reporter: Ashutosh Chauhan
>
> Token signature should be sent from client to tasks and then used to get the
> tokens
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
