<a href="../../hadoop-mapreduce-client/hadoop-mapreduce-client-core/MapReduce_Compatibility_Hadoop1_Hadoop2.html">Compatibilty between Hadoop 1.x and Hadoop 2.x</a>
<a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
<img alt="Built by Maven" src="./images/logos/maven-feather.png"/>
</a>
</div>
</div>
<div id="bodyColumn">
<div id="contentBox">
<!-- Licensed under the Apache License, Version 2.0 (the "License"); --><!-- you may not use this file except in compliance with the License. --><!-- You may obtain a copy of the License at --><!-- --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!-- --><!-- Unless required by applicable law or agreed to in writing, software --><!-- distributed under the License is distributed on an "AS IS" BASIS, --><!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. --><!-- See the License for the specific language governing permissions and --><!-- limitations under the License. See accompanying LICENSE file. --><div class="section">
<h2>Authentication for Hadoop HTTP web-consoles<a name="Authentication_for_Hadoop_HTTP_web-consoles"></a></h2>
<ul>
<li><a href="#Authentication_for_Hadoop_HTTP_web-consoles">Authentication for Hadoop HTTP web-consoles</a>
<p>This document describes how to configure Hadoop HTTP web-consoles to require user authentication.</p>
<p>By default Hadoop HTTP web-consoles (JobTracker, NameNode, TaskTrackers and DataNodes) allow access without any form of authentication.</p>
<p>Similarly to Hadoop RPC, Hadoop HTTP web-consoles can be configured to require Kerberos authentication using HTTP SPNEGO protocol (supported by browsers like Firefox and Internet Explorer).</p>
<p>In addition, Hadoop HTTP web-consoles support the equivalent of Hadoop's Pseudo/Simple authentication. If this option is enabled, user must specify their user name in the first browser interaction using the user.name query string parameter. For example: <tt>http://localhost:50030/jobtracker.jsp?user.name=babu</tt>.</p>
<p>If a custom authentication mechanism is required for the HTTP web-consoles, it is possible to implement a plugin to support the alternate authentication mechanism (refer to Hadoop hadoop-auth for details on writing an <tt>AuthenticatorHandler</tt>).</p>
<p>The next section describes how to configure Hadoop HTTP web-consoles to require user authentication.</p></div>
<p>The following properties should be in the <tt>core-site.xml</tt> of all the nodes in the cluster.</p>
<p><tt>hadoop.http.filter.initializers</tt>: add to this property the <tt>org.apache.hadoop.security.AuthenticationFilterInitializer</tt> initializer class.</p>
<p><tt>hadoop.http.authentication.type</tt>: Defines authentication used for the HTTP web-consoles. The supported values are: <tt>simple</tt> | <tt>kerberos</tt> | <tt>#AUTHENTICATION_HANDLER_CLASSNAME#</tt>. The dfeault value is <tt>simple</tt>.</p>
<p><tt>hadoop.http.authentication.token.validity</tt>: Indicates how long (in seconds) an authentication token is valid before it has to be renewed. The default value is <tt>36000</tt>.</p>
<p><tt>hadoop.http.authentication.signature.secret.file</tt>: The signature secret file for signing the authentication tokens. The same secret should be used for all nodes in the cluster, JobTracker, NameNode, DataNode and TastTracker. The default value is <tt>$<a name="user.home">user.home</a>/hadoop-http-auth-signature-secret</tt>. IMPORTANT: This file should be readable only by the Unix user running the daemons.</p>
<p><tt>hadoop.http.authentication.cookie.domain</tt>: The domain to use for the HTTP cookie that stores the authentication token. In order to authentiation to work correctly across all nodes in the cluster the domain must be correctly set. There is no default value, the HTTP cookie will not have a domain working only with the hostname issuing the HTTP cookie.</p>
<p>IMPORTANT: when using IP addresses, browsers ignore cookies with domain settings. For this setting to work properly all nodes in the cluster must be configured to generate URLs with <tt>hostname.domain</tt> names on it.</p>
<p><tt>hadoop.http.authentication.simple.anonymous.allowed</tt>: Indicates if anonymous requests are allowed when using 'simple' authentication. The default value is <tt>true</tt></p>
<p><tt>hadoop.http.authentication.kerberos.principal</tt>: Indicates the Kerberos principal to be used for HTTP endpoint when using 'kerberos' authentication. The principal short name must be <tt>HTTP</tt> per Kerberos HTTP SPNEGO specification. The default value is <tt>HTTP/_HOST@$LOCALHOST</tt>, where <tt>_HOST</tt> -if present- is replaced with bind address of the HTTP server.</p>
<p><tt>hadoop.http.authentication.kerberos.keytab</tt>: Location of the keytab file with the credentials for the Kerberos principal used for the HTTP endpoint. The default value is <tt>$<a name="user.home">user.home</a>/hadoop.keytab</tt>.i</p></div></div>