<ahref="../hadoop-mapreduce-client/hadoop-mapreduce-client-core/MapReduce_Compatibility_Hadoop1_Hadoop2.html">Compatibilty between Hadoop 1.x and Hadoop 2.x</a>
<ahref="http://maven.apache.org/"title="Built by Maven"class="poweredBy">
<imgalt="Built by Maven"src="./images/logos/maven-feather.png"/>
</a>
</div>
</div>
<divid="bodyColumn">
<divid="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. --><divclass="section">
<h2>Hadoop HDFS over HTTP 2.3.0 - Using HTTP Tools<aname="Hadoop_HDFS_over_HTTP_2.3.0_-_Using_HTTP_Tools"></a></h2>
<p>[ <ahref="./index.html">Go Back</a> ]</p>
<divclass="section">
<h3>Security<aname="Security"></a></h3>
<p>Out of the box HttpFS supports both pseudo authentication and Kerberos HTTP SPNEGO authentication.</p>
<p>With pseudo authentication the user name must be specified in the <tt>user.name=<USERNAME></tt> query string parameter of a HttpFS URL. For example:</p>
<p>NOTE: the <tt>-u USER</tt> option is required by the <tt>--negotiate</tt> but it is not used. Use any value as <tt>USER</tt> and when asked for the password press [ENTER] as the password value is ignored.</p></div>
<divclass="section">
<h4><aname="Remembering_Who_I_Am">Remembering Who I Am</a> (Establishing an Authenticated Session)<aname="Remembering_Who_I_Am_Establishing_an_Authenticated_Session"></a></h4>
<p>As most authentication mechanisms, Hadoop HTTP authentication authenticates users once and issues a short-lived authentication token to be presented in subsequent requests. This authentication token is a signed HTTP Cookie.</p>
<p>When using tools like <tt>curl</tt>, the authentication token must be stored on the first request doing authentication, and submitted in subsequent requests. To do this with curl the <tt>-b</tt> and <tt>-c</tt> options to save and send HTTP Cookies must be used.</p>
<p>For example, the first request doing authentication should save the received HTTP Cookies.</p>