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

Posted to common-dev@hadoop.apache.org by "Pankaj (JIRA)" <ji...@apache.org> on 2019/05/06 22:51:00 UTC

[jira] [Created] (HADOOP-16298) Manage/Renew delegation tokens for externally scheduled jobs

Pankaj created HADOOP-16298:
-------------------------------

             Summary: 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: common
    Affects Versions: 3.2.0, 2.9.0, 2.7.3, 3.3.0
            Reporter: Pankaj
             Fix For: 3.3.0, 3.2.0, 2.9.0, 2.7.3
         Attachments: Proposal for changes to UGI for managing_renewing externally managed delegation tokens.pdf

* 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org