Authorization and Authentication in Hadoop
Everything from authentication to authorization at HDFS, MapReduce, NameNode and JobTacker level explained:
In the context of MapReduce, the users and groups are used to determine who is allowed to submit or modify jobs. In MapReduce, jobs are submitted via queues controlled by the scheduler. Administrators can define who is allowed to submit jobs to particular queues via MapReduce ACLs. These ACLs can also be defined on a job-by-job basis. Similar to the HDFS permissions, if the specified users or groups don’t exist, the queues will be unusable, except by superusers, who are always authorized to submit or modify jobs. […]
When a user runs a hadoop command, the NameNode or JobTracker gets some information about the user running that command. Most importantly, it knows the username of the user. The daemons then use that username to determine what groups the user belongs to. This is done through the use of a pluggable interface, which has the ability to take a username and map it to a set of groups that the user belongs to.
Original title and link: Authorization and Authentication in Hadoop (©myNoSQL)
via: http://www.cloudera.com/blog/2012/03/authorization-and-authentication-in-hadoop/
