hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8572) Have the ability to force the use of the login user
Date Tue, 10 Jul 2012 16:56:35 GMT

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

Daryn Sharp commented on HADOOP-8572:

Could this issue be addressed by {{UserGroupInformation.getLoginUser().doAs(...)}}?
> Have the ability to force the use of the login user 
> ----------------------------------------------------
>                 Key: HADOOP-8572
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8572
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Guillaume Nodet
>         Attachments: HADOOP-8572.patch
> In Karaf, most of the code is run under the "karaf" user. When a user ssh into Karaf,
commands will be executed under that user.
> Deploying hadoop inside Karaf requires that the authenticated Subject has the required
hadoop principals set, which forces the reconfiguration of the whole security layer, even
at dev time.
> My patch proposes the introduction of a new configuration property {{hadoop.security.force.login.user}}
which if set to true (it would default to false to keep the current behavior), would force
the use of the login user instead of using the authenticated subject (which is what happen
when there's no authenticated subject at all).  This greatly simplifies the use of hadoop
in such environments where security isn't really needed (at dev time).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message