[HADOOP-8572] Have the ability to force the use of the login user

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Guillaume Nodet
• Created: 06/Jul/12 14:04
• Updated: 22/May/14 08:32

Description

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).

Issue Links

• is related to: HADOOP-7101 UserGroupInformation.getCurrentUser() fails when called from non-Hadoop JAAS context
• relates to: HADOOP-7977 Allow Hadoop clients and services to run in an OSGi container