hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14808) Hadoop keychain
Date Fri, 25 Aug 2017 16:54:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141863#comment-16141863

Steve Loughran commented on HADOOP-14808:

for things like S3A, I don't actually want to pass my long-lived tokens around...I either
want to propagate any session tokens, or create a new set (which is what HADOOP-14556) does.
Which makes be think the way to view these credentials are similar to DTs: serializable secrets
which have limited lifespans

> Hadoop keychain
> ---------------
>                 Key: HADOOP-14808
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14808
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: security
>    Affects Versions: 2.7.0
>            Reporter: John Zhuge
>            Assignee: John Zhuge
> Extend the idea from HADOOP-6520 "UGI should load tokens from the environment" to a generic
lightweight "keychain" design. Load keys (secrets) into a keychain in UGI (secret map) at
startup. YARN will distribute them securely into each container. The Hadoop code running in
the container can then retrieve the credentials from UGI.
> The use case is Bring Your Own Key (BYOK) credentials for cloud connectors (adl, wasb,
s3a, etc.), while Hadoop authentication is still Kerberos. No configuration change, no admin
involved. It will support YARN applications initially, e.g., DistCp, Tera Suite, Spark-on-Yarn,
> Implementation is surprisingly simple because almost all pieces are in place:
> * Retrieve secrets from UGI using {{conf.getPassword}} backed by the existing Credential
Provider class {{UserProvider}}
> * Reuse Credential Provider classes and interface to define local permanent or transient
credential store, e.g., {{LocalJavaKeyStoreProvider}}
> * New: create a new transient Credential Provider that logs into AAD with username/password
or device code, and then put the Client ID and Refresh Token into the keychain
> * New: create a new permanent Credential Provider based on Hadoop configuration XML,
for dev/testing purpose.
> Links
> * HADOOP-11766 Generic token authentication support for Hadoop
> * HADOOP-11744 Support OAuth2 in Hadoop
> * HADOOP-10959 A Kerberos based token authentication approach
> * HADOOP-9392 Token based authentication and Single Sign On

This message was sent by Atlassian JIRA

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

View raw message