[
https://issues.apache.org/jira/browse/HADOOP-16298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038602#comment-18038602
]
ASF GitHub Bot commented on HADOOP-16298:
-----------------------------------------
github-actions[bot] closed pull request #4059: HADOOP-16298. Manage/Renew
delegation tokens for externally scheduled jobs
URL: https://github.com/apache/hadoop/pull/4059
> Manage/Renew delegation tokens for externally scheduled jobs
> ------------------------------------------------------------
>
> Key: HADOOP-16298
> URL: https://issues.apache.org/jira/browse/HADOOP-16298
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 3.3.0
> Reporter: Pankaj Deshpande
> Assignee: Clay B.
> Priority: Major
> Labels: pull-request-available
> Attachments: Proposal for changes to UGI for managing_renewing
> externally managed delegation tokens.pdf
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Presently when jobs are run in the Hadoop ecosystem, the implicit
> assumption is that YARN will be used as a scheduling agent with access to
> appropriate keytabs for renewal of kerberos tickets and delegation tokens.
> * Jobs that interact with kerberized hadoop services such as hbase/hive/hdfs
> and use an external scheduler such as Kubernetes, typically do not have
> access to keytabs. In such cases, delegation tokens are a logical choice for
> interacting with a kerberized cluster. These tokens are issued based on some
> external auth mechanism (such as Kube LDAP authentication).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
