You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@knox.apache.org by su...@apache.org on 2015/05/26 18:07:09 UTC
svn commit: r1681785 [3/8] - in /knox: site/ site/books/knox-0-7-0/ trunk/
trunk/books/0.7.0/ trunk/books/0.7.0/dev-guide/
Added: knox/site/books/knox-0-7-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-7-0/user-guide.html?rev=1681785&view=auto
==============================================================================
--- knox/site/books/knox-0-7-0/user-guide.html (added)
+++ knox/site/books/knox-0-7-0/user-guide.html Tue May 26 16:07:07 2015
@@ -0,0 +1,3623 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+--><p><link href="book.css" rel="stylesheet"/></p><p><img src="knox-logo.gif" alt="Knox"/> <!-- <img src="apache-logo.gif" alt="Apache"/> --> <img src="apache-logo.gif" align="right" alt="Apache"/></p><h1><a id="Apache+Knox+Gateway+0.6.x+User's+Guide"></a>Apache Knox Gateway 0.6.x User’s Guide</h1><h2><a id="Table+Of+Contents"></a>Table Of Contents</h2>
+<ul>
+ <li><a href="#Introduction">Introduction</a></li>
+ <li><a href="#Quick+Start">Quick Start</a></li>
+ <li><a href="#Gateway+Samples">Gateway Samples</a></li>
+ <li><a href="#Apache+Knox+Details">Apache Knox Details</a>
+ <ul>
+ <li><a href="#Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a></li>
+ <li><a href="#Supported+Services">Supported Services</a></li>
+ </ul></li>
+ <li><a href="#Gateway+Details">Gateway Details</a>
+ <ul>
+ <li><a href="#URL+Mapping">URL Mapping</a></li>
+ <li><a href="#Configuration">Configuration</a></li>
+ <li><a href="#Knox+CLI">Knox CLI</a></li>
+ <li><a href="#Admin+API">Admin API</a></li>
+ <li><a href="#Authentication">Authentication</a></li>
+ <li><a href="#Advanced+LDAP+Authentication">Advanced LDAP Authentication</a></li>
+ <li><a href="#LDAP+Authentication+Caching">LDAP Authentication Caching</a></li>
+ <li><a href="#LDAPGroupLookup">LDAPGroupLookup</a></li>
+ <li><a href="#Identity+Assertion">Identity Assertion</a></li>
+ <li><a href="#Authorization">Authorization</a></li>
+ <li><a href="#Secure+Clusters">Secure Clusters</a></li>
+ <li><a href="#High+Availability">High Availability</a></li>
+ <li><a href="#Web+App+Security+Provider">Web App Security Provider</a></li>
+ <li><a href="#Preauthenticated+SSO+Provider">Preauthenticated SSO Provider</a></li>
+ <li><a href="#Audit">Audit</a></li>
+ </ul></li>
+ <li><a href="#Client+Details">Client Details</a></li>
+ <li><a href="#Service+Details">Service Details</a>
+ <ul>
+ <li><a href="#WebHDFS">WebHDFS</a></li>
+ <li><a href="#WebHCat">WebHCat</a></li>
+ <li><a href="#Oozie">Oozie</a></li>
+ <li><a href="#HBase">HBase</a></li>
+ <li><a href="#Hive">Hive</a></li>
+ <li><a href="#Yarn">Yarn</a></li>
+ <li><a href="#Storm">Storm</a></li>
+ </ul></li>
+ <li><a href="#Limitations">Limitations</a></li>
+ <li><a href="#Troubleshooting">Troubleshooting</a></li>
+ <li><a href="#Export+Controls">Export Controls</a></li>
+</ul><h2><a id="Introduction"></a>Introduction</h2><p>The Apache Knox Gateway is a system that provides a single point of authentication and access for Apache Hadoop services in a cluster. The goal is to simplify Hadoop security for both users (i.e. who access the cluster data and execute jobs) and operators (i.e. who control access and manage the cluster). The gateway runs as a server (or cluster of servers) that provide centralized access to one or more Hadoop clusters. In general the goals of the gateway are as follows:</p>
+<ul>
+ <li>Provide perimeter security for Hadoop REST APIs to make Hadoop security easier to setup and use
+ <ul>
+ <li>Provide authentication and token verification at the perimeter</li>
+ <li>Enable authentication integration with enterprise and cloud identity management systems</li>
+ <li>Provide service level authorization at the perimeter</li>
+ </ul></li>
+ <li>Expose a single URL hierarchy that aggregates REST APIs of a Hadoop cluster
+ <ul>
+ <li>Limit the network endpoints (and therefore firewall holes) required to access a Hadoop cluster</li>
+ <li>Hide the internal Hadoop cluster topology from potential attackers</li>
+ </ul></li>
+</ul><h2><a id="Quick+Start"></a>Quick Start</h2><p>Here are the steps to have Apache Knox up and running against a Hadoop Cluster:</p>
+<ol>
+ <li>Verify system requirements</li>
+ <li>Download a virtual machine (VM) with Hadoop</li>
+ <li>Download Apache Knox Gateway</li>
+ <li>Start the virtual machine with Hadoop</li>
+ <li>Install Knox</li>
+ <li>Start the LDAP embedded within Knox</li>
+ <li>Start the Knox Gateway</li>
+ <li>Do Hadoop with Knox</li>
+</ol><h3><a id="1+-+Requirements"></a>1 - Requirements</h3><h4><a id="Java"></a>Java</h4><p>Java 1.6 or later is required for the Knox Gateway runtime. Use the command below to check the version of Java installed on the system where Knox will be running.</p>
+<pre><code>java -version
+</code></pre><h4><a id="Hadoop"></a>Hadoop</h4><p>Knox 0.6.0 supports Hadoop 2.x, the quick start instructions assume a Hadoop 2.x virtual machine based environment.</p><h3><a id="2+-+Download+Hadoop+2.x+VM"></a>2 - Download Hadoop 2.x VM</h3><p>The quick start provides a link to download Hadoop 2.0 based Hortonworks virtual machine <a href="http://hortonworks.com/products/hdp-2/#install">Sandbox</a>. Please note Knox supports other Hadoop distributions and is configurable against a full blown Hadoop cluster. Configuring Knox for Hadoop 2.x version, or Hadoop deployed in EC2 or a custom Hadoop cluster is documented in advance deployment guide.</p><h3><a id="3+-+Download+Apache+Knox+Gateway"></a>3 - Download Apache Knox Gateway</h3><p>Download one of the distributions below from the <a href="http://www.apache.org/dyn/closer.cgi/knox">Apache mirrors</a>.</p>
+<ul>
+ <li>Source archive: <a href="http://www.apache.org/dyn/closer.cgi/knox/0.6.0/knox-0.6.0-src.zip">knox-0.6.0-src.zip</a> (<a href="http://www.apache.org/dyn/closer.cgi/knox/0.6.0/knox-0.6.0-src.zip.asc">PGP signature</a>, <a href="http://www.apache.org/dyn/closer.cgi/knox/0.6.0/knox-0.6.0-src.zip.sha">SHA1 digest</a>, <a href="http://www.apache.org/dyn/closer.cgi/knox/0.6.0/knox-0.6.0-src.zip.md5">MD5 digest</a>)</li>
+ <li>Binary archive: <a href="http://www.apache.org/dyn/closer.cgi/knox/0.6.0/knox-0.6.0.zip">knox-0.6.0.zip</a> (<a href="http://www.apache.org/dyn/closer.cgi/knox/0.6.0/knox-0.6.0.zip.asc">PGP signature</a>, <a href="http://www.apache.org/dyn/closer.cgi/knox/0.6.0/knox-0.6.0.zip.sha">SHA1 digest</a>, <a href="http://www.apache.org/dyn/closer.cgi/knox/0.6.0/knox-0.6.0.zip.md5">MD5 digest</a>)</li>
+</ul><p>Apache Knox Gateway releases are available under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>. See the NOTICE file contained in each release artifact for applicable copyright attribution notices.</p><h3><a id="Verify"></a>Verify</h3><p>While recommended, verify is an optional step. You can verify the integrity of any downloaded files using the PGP signatures. Please read <a href="http://httpd.apache.org/dev/verification.html">Verifying Apache HTTP Server Releases</a> for more information on why you should verify our releases.</p><p>The PGP signatures can be verified using PGP or GPG. First download the <a href="https://dist.apache.org/repos/dist/release/knox/KEYS">KEYS</a> file as well as the .asc signature files for the relevant release packages. Make sure you get these files from the main distribution directory linked above, rather than from a mirror. Then verify the signatures using one of the methods below.</p>
+<pre><code>% pgpk -a KEYS
+% pgpv knox-0.6.0.zip.asc
+</code></pre><p>or</p>
+<pre><code>% pgp -ka KEYS
+% pgp knox-0.6.0.zip.asc
+</code></pre><p>or</p>
+<pre><code>% gpg --import KEYS
+% gpg --verify knox-0.6.0.zip.asc
+</code></pre><h3><a id="4+-+Start+Hadoop+virtual+machine"></a>4 - Start Hadoop virtual machine</h3><p>Start the Hadoop virtual machine.</p><h3><a id="5+-+Install+Knox"></a>5 - Install Knox</h3><p>The steps required to install the gateway will vary depending upon which distribution format (zip | rpm) was downloaded. In either case you will end up with a directory where the gateway is installed. This directory will be referred to as your <code>{GATEWAY_HOME}</code> throughout this document.</p><h4><a id="ZIP"></a>ZIP</h4><p>If you downloaded the Zip distribution you can simply extract the contents into a directory. The example below provides a command that can be executed to do this. Note the <code>{VERSION}</code> portion of the command must be replaced with an actual Apache Knox Gateway version number. This might be 0.6.0 for example.</p>
+<pre><code>unzip knox-{VERSION}.zip
+</code></pre><p>This will create a directory <code>knox-{VERSION}</code> in your current directory. The directory <code>knox-{VERSION}</code> will considered your <code>{GATEWAY_HOME}</code></p><h3><a id="6+-+Start+LDAP+embedded+in+Knox"></a>6 - Start LDAP embedded in Knox</h3><p>Knox comes with an LDAP server for demonstration purposes. Note: If the tool used to extract the contents of the Tar or tar.gz file was not capable of making the files in the bin directory executable</p>
+<pre><code>cd {GATEWAY_HOME}
+bin/ldap.sh start
+</code></pre><h3><a id="7+-+Create+the+Master+Secret"></a>7 - Create the Master Secret</h3><p>Run the knoxcli create-master command in order to persist the master secret that is used to protect the key and credential stores for the gateway instance.</p>
+<pre><code>cd {GATEWAY_HOME}
+bin/knoxcli.sh create-master
+</code></pre><p>The cli will prompt you for the master secret (i.e. password).</p><h3><a id="7+-+Start+Knox"></a>7 - Start Knox</h3><p>The gateway can be started using the provided shell script.</p><p>The server will discover the persisted master secret during start up and complete the setup process for demo installs. A demo install will consist of a knox gateway instance with an identity certificate for localhost. This will require clients to be on the same machine or to turn off hostname verification. For more involved deployments, See the Knox CLI section of this document for additional configuration options, including the ability to create a self-signed certificate for a specific hostname.</p>
+<pre><code>cd {GATEWAY_HOME}
+bin/gateway.sh start
+</code></pre><p>When starting the gateway this way the process will be run in the background. The log files will be written to {GATEWAY_HOME}/logs and the process ID files (PIDS) will b written to {GATEWAY_HOME}/pids.</p><p>In order to stop a gateway that was started with the script use this command.</p>
+<pre><code>cd {GATEWAY_HOME}
+bin/gateway.sh stop
+</code></pre><p>If for some reason the gateway is stopped other than by using the command above you may need to clear the tracking PID.</p>
+<pre><code>cd {GATEWAY_HOME}
+bin/gateway.sh clean
+</code></pre><p><strong>NOTE: This command will also clear any .out and .err file from the {GATEWAY_HOME}/logs directory so use this with caution.</strong></p><h3><a id="8+-+Do+Hadoop+with+Knox"></a>8 - Do Hadoop with Knox</h3><h4><a id="Invoke+the+LISTSTATUS+operation+on+WebHDFS+via+the+gateway."></a>Invoke the LISTSTATUS operation on WebHDFS via the gateway.</h4><p>This will return a directory listing of the root (i.e. /) directory of HDFS.</p>
+<pre><code>curl -i -k -u guest:guest-password -X GET \
+ 'https://localhost:8443/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS'
+</code></pre><p>The results of the above command should result in something to along the lines of the output below. The exact information returned is subject to the content within HDFS in your Hadoop cluster. Successfully executing this command at a minimum proves that the gateway is properly configured to provide access to WebHDFS. It does not necessarily provide that any of the other services are correct configured to be accessible. To validate that see the sections for the individual services in <a href="#Service+Details">Service Details</a>.</p>
+<pre><code>HTTP/1.1 200 OK
+Content-Type: application/json
+Content-Length: 760
+Server: Jetty(6.1.26)
+
+{"FileStatuses":{"FileStatus":[
+{"accessTime":0,"blockSize":0,"group":"hdfs","length":0,"modificationTime":1350595859762,"owner":"hdfs","pathSuffix":"apps","permission":"755","replication":0,"type":"DIRECTORY"},
+{"accessTime":0,"blockSize":0,"group":"mapred","length":0,"modificationTime":1350595874024,"owner":"mapred","pathSuffix":"mapred","permission":"755","replication":0,"type":"DIRECTORY"},
+{"accessTime":0,"blockSize":0,"group":"hdfs","length":0,"modificationTime":1350596040075,"owner":"hdfs","pathSuffix":"tmp","permission":"777","replication":0,"type":"DIRECTORY"},
+{"accessTime":0,"blockSize":0,"group":"hdfs","length":0,"modificationTime":1350595857178,"owner":"hdfs","pathSuffix":"user","permission":"755","replication":0,"type":"DIRECTORY"}
+]}}
+</code></pre><h4><a id="Put+a+file+in+HDFS+via+Knox."></a>Put a file in HDFS via Knox.</h4>
+<pre><code>curl -i -k -u guest:guest-password -X PUT \
+ 'https://localhost:8443/gateway/sandbox/webhdfs/v1/tmp/LICENSE?op=CREATE'
+
+curl -i -k -u guest:guest-password -T LICENSE -X PUT \
+ '{Value of Location header from response response above}'
+</code></pre><h4><a id="Get+a+file+in+HDFS+via+Knox."></a>Get a file in HDFS via Knox.</h4>
+<pre><code>curl -i -k -u guest:guest-password -X GET \
+ 'https://localhost:8443/gateway/sandbox/webhdfs/v1/tmp/LICENSE?op=OPEN'
+
+curl -i -k -u guest:guest-password -X GET \
+ '{Value of Location header from command response above}'
+</code></pre><h2><a id="Apache+Knox+Details"></a>Apache Knox Details</h2><p>This section provides everything you need to know to get the Knox gateway up and running against a Hadoop cluster.</p><h4><a id="Hadoop"></a>Hadoop</h4><p>An existing Hadoop 2.x cluster is required for Knox 0.6.0 to sit in front of and protect. It is possible to use a Hadoop cluster deployed on EC2 but this will require additional configuration not covered here. It is also possible to protect access to a services of a Hadoop cluster that is secured with kerberos. This too requires additional configuration that is described in other sections of this guide. See <a href="#Supported+Services">Supported Services</a> for details on what is supported for this release.</p><p>The Hadoop cluster should be ensured to have at least WebHDFS, WebHCat (i.e. Templeton) and Oozie configured, deployed and running. HBase/Stargate and Hive can also be accessed via the Knox Gateway given the proper versions and configuration.</p
><p>The instructions that follow assume a few things:</p>
+<ol>
+ <li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
+ <li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout"></a>Apache Knox Directory Layout</h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+<table>
+ <thead>
+ <tr>
+ <th>Directory </th>
+ <th>Purpose </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>conf/ </td>
+ <td>Contains configuration files that apply to the gateway globally (i.e. not cluster specific ). </td>
+ </tr>
+ <tr>
+ <td>data/ </td>
+ <td>Contains security and topology specific artifacts that require read/write access at runtime </td>
+ </tr>
+ <tr>
+ <td>conf/topologies/ </td>
+ <td>Contains topology files that represent Hadoop clusters which the gateway uses to deploy cluster proxies </td>
+ </tr>
+ <tr>
+ <td>data/security/ </td>
+ <td>Contains the persisted master secret and keystore dir </td>
+ </tr>
+ <tr>
+ <td>data/security/keystores/ </td>
+ <td>Contains the gateway identity keystore and credential stores for the gateway and each deployed cluster topology </td>
+ </tr>
+ <tr>
+ <td>data/services </td>
+ <td>Contains service behavior definitions for the services currently supported. </td>
+ </tr>
+ <tr>
+ <td>bin/ </td>
+ <td>Contains the executable shell scripts, batch files and JARs for clients and servers. </td>
+ </tr>
+ <tr>
+ <td>data/deployments/ </td>
+ <td>Contains deployed cluster topologies used to protect access to specific Hadoop clusters. </td>
+ </tr>
+ <tr>
+ <td>lib/ </td>
+ <td>Contains the JARs for all the components that make up the gateway. </td>
+ </tr>
+ <tr>
+ <td>dep/ </td>
+ <td>Contains the JARs for all of the components upon which the gateway depends. </td>
+ </tr>
+ <tr>
+ <td>ext/ </td>
+ <td>A directory where user supplied extension JARs can be placed to extends the gateways functionality. </td>
+ </tr>
+ <tr>
+ <td>pids/ </td>
+ <td>Contains the process ids for running ldap and gateway servers </td>
+ </tr>
+ <tr>
+ <td>samples/ </td>
+ <td>Contains a number of samples that can be used to explore the functionality of the gateway. </td>
+ </tr>
+ <tr>
+ <td>templates/ </td>
+ <td>Contains default configuration files that can be copied and customized. </td>
+ </tr>
+ <tr>
+ <td>README </td>
+ <td>Provides basic information about the Apache Knox Gateway. </td>
+ </tr>
+ <tr>
+ <td>ISSUES </td>
+ <td>Describes significant know issues. </td>
+ </tr>
+ <tr>
+ <td>CHANGES </td>
+ <td>Enumerates the changes between releases. </td>
+ </tr>
+ <tr>
+ <td>LICENSE </td>
+ <td>Documents the license under which this software is provided. </td>
+ </tr>
+ <tr>
+ <td>NOTICE </td>
+ <td>Documents required attribution notices for included dependencies. </td>
+ </tr>
+ </tbody>
+</table><h3><a id="Supported+Services"></a>Supported Services</h3><p>This table enumerates the versions of various Hadoop services that have been tested to work with the Knox Gateway.</p>
+<table>
+ <thead>
+ <tr>
+ <th>Service </th>
+ <th>Version </th>
+ <th>Non-Secure </th>
+ <th>Secure </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>WebHDFS </td>
+ <td>2.4.0 </td>
+ <td><img src="check.png" alt="y"/> </td>
+ <td><img src="check.png" alt="y"/> </td>
+ </tr>
+ <tr>
+ <td>WebHCat/Templeton </td>
+ <td>0.13.0 </td>
+ <td><img src="check.png" alt="y"/> </td>
+ <td><img src="check.png" alt="y"/> </td>
+ </tr>
+ <tr>
+ <td>Oozie </td>
+ <td>4.0.0 </td>
+ <td><img src="check.png" alt="y"/> </td>
+ <td><img src="check.png" alt="y"/> </td>
+ </tr>
+ <tr>
+ <td>HBase/Stargate </td>
+ <td>0.98.0 </td>
+ <td><img src="check.png" alt="y"/> </td>
+ <td><img src="check.png" alt="y"/> </td>
+ </tr>
+ <tr>
+ <td>Hive (via WebHCat) </td>
+ <td>0.13.0 </td>
+ <td><img src="check.png" alt="y"/> </td>
+ <td><img src="check.png" alt="y"/> </td>
+ </tr>
+ <tr>
+ <td>Hive (via JDBC/ODBC) </td>
+ <td>0.13.0 </td>
+ <td><img src="check.png" alt="y"/> </td>
+ <td><img src="check.png" alt="y"/> </td>
+ </tr>
+ <tr>
+ <td>Yarn ResourceManager </td>
+ <td>2.5.0 </td>
+ <td><img src="check.png" alt="y"/> </td>
+ <td><img src="check.png" alt="y"/> </td>
+ </tr>
+ <tr>
+ <td>Storm </td>
+ <td>0.9.3 </td>
+ <td><img src="check.png" alt="y"/> </td>
+ <td><img src="error.png" alt="n"/> </td>
+ </tr>
+ </tbody>
+</table><h3><a id="More+Examples"></a>More Examples</h3><p>These examples provide more detail about how to access various Apache Hadoop services via the Apache Knox Gateway.</p>
+<ul>
+ <li><a href="#WebHDFS+Examples">WebHDFS Examples</a></li>
+ <li><a href="#WebHCat+Examples">WebHCat Examples</a></li>
+ <li><a href="#Oozie+Examples">Oozie Examples</a></li>
+ <li><a href="#HBase+Examples">HBase Examples</a></li>
+ <li><a href="#Hive+Examples">Hive Examples</a></li>
+ <li><a href="#Yarn+Examples">Yarn Examples</a></li>
+ <li><a href="#Storm+Examples">Storm Examples</a></li>
+</ul><h3><a id="Gateway+Samples"></a>Gateway Samples</h3><p>The purpose of the samples within the {GATEWAY_HOME}/samples directory is to demonstrate the capabilities of the Apache Knox Gateway to provide access to the numerous APIs that are available from the service components of a Hadoop cluster.</p><p>Depending on exactly how your Knox installation was done, there will be some number of steps required in order fully install and configure the samples for use.</p><p>This section will help describe the assumptions of the samples and the steps to get them to work in a couple of different deployment scenarios.</p><h4><a id="Assumptions+of+the+Samples"></a>Assumptions of the Samples</h4><p>The samples were initially written with the intent of working out of the box for the various Hadoop demo environments that are deployed as a single node cluster inside of a VM. The following assumptions were made from that context and should be understood in order to get the samples to work in other
deployment scenarios:</p>
+<ul>
+ <li>That there is a valid java JDK on the PATH for executing the samples</li>
+ <li>The Knox Demo LDAP server is running on localhost and port 33389 which is the default port for the ApacheDS LDAP server.</li>
+ <li>That the LDAP directory in use has a set of demo users provisioned with the convention of username and username“-password” as the password. Most of the samples have some variation of this pattern with “guest” and “guest-password”.</li>
+ <li>That the Knox Gateway instance is running on the same machine which you will be running the samples from - therefore “localhost” and that the default port of “8443” is being used.</li>
+ <li>Finally, that there is a properly provisioned sandbox.xml topology in the {GATEWAY_HOME}/conf/topologies directory that is configured to point to the actual host and ports of running service components.</li>
+</ul><h4><a id="Steps+for+Demo+Single+Node+Clusters"></a>Steps for Demo Single Node Clusters</h4><p>There should be little to do if anything in a demo environment that has been provisioned with illustrating the use of Apache Knox.</p><p>However, the following items will be worth ensuring before you start:</p>
+<ol>
+ <li>The sandbox.xml topology is configured properly for the deployed services</li>
+ <li>That there is an LDAP server running with guest/guest-password user available in the directory</li>
+</ol><h4><a id="Steps+for+Ambari+Deployed+Knox+Gateway"></a>Steps for Ambari Deployed Knox Gateway</h4><p>Apache Knox instances that are under the management of Ambari are generally assumed not to be demo instances. These instances are in place to facilitate development, testing or production Hadoop clusters.</p><p>The Knox samples can however be made to work with Ambari managed Knox instances with a few steps:</p>
+<ol>
+ <li>You need to have ssh access to the environment in order for the localhost assumption within the samples to be valid.</li>
+ <li>The Knox Demo LDAP Server is started - you can start it from Ambari</li>
+ <li>The default.xml topology file can be copied to sandbox.xml in order to satisfy the topology name assumption in the samples.</li>
+ <li><p>Be sure to use an actual Java JRE to run the sample with something like:</p><p>/usr/jdk64/jdk1.7.0_67/bin/java -jar bin/shell.jar samples/ExampleWebHdfsLs.groovy</p></li>
+</ol><h4><a id="Steps+for+a+Manually+Installed+Knox+Gateway"></a>Steps for a Manually Installed Knox Gateway</h4><p>For manually installed Knox instances, there is really no way for the installer to know how to configure the topology file for you.</p><p>Essentially, these steps are identical to the Amabari deployed instance except that #3 should be replaced with the configuration of the ootb sandbox.xml to point the configuration at the proper hosts and ports.</p>
+<ol>
+ <li>You need to have ssh access to the environment in order for the localhost assumption within the samples to be valid.</li>
+ <li>The Knox Demo LDAP Server is started - you can start it from Ambari</li>
+ <li>Change the hosts and ports within the {GATEWAY_HOME}/conf/topologies/sandbox.xml to reflect your actual cluster service locations.</li>
+ <li><p>Be sure to use an actual Java JRE to run the sample with something like:</p><p>/usr/jdk64/jdk1.7.0_67/bin/java -jar bin/shell.jar samples/ExampleWebHdfsLs.groovy</p></li>
+</ol><h2><a id="Gateway+Details"></a>Gateway Details</h2><p>This section describes the details of the Knox Gateway itself. Including: </p>
+<ul>
+ <li>How URLs are mapped between a gateway that services multiple Hadoop clusters and the clusters themselves</li>
+ <li>How the gateway is configured through gateway-site.xml and cluster specific topology files</li>
+ <li>How to configure the various policy enfocement provider features such as authentication, authorization, auditing, hostmapping, etc.</li>
+</ul><h3><a id="URL+Mapping"></a>URL Mapping</h3><p>The gateway functions much like a reverse proxy. As such, it maintains a mapping of URLs that are exposed externally by the gateway to URLs that are provided by the Hadoop cluster.</p><h4><a id="Default+Topology+URLs"></a>Default Topology URLs</h4><p>In order to provide compatibility with the Hadoop java client and existing CLI tools, the Knox Gateway has provided a feature called the Default Topology. This refers to a topology deployment that will be able to route URLs without the additional context that the gateway uses for differentiating from one Hadoop cluster to another. This allows the URLs to match those used by existing clients for that may access webhdfs through the Hadoop file system abstraction.</p><p>When a topology file is deployed with a file name that matches the configured default topology name, a specialized mapping for URLs is installed for that particular topology. This allows the URLs that are expected by the e
xisting Hadoop CLIs for webhdfs to be used in interacting with the specific Hadoop cluster that is represented by the default topology file.</p><p>The configuration for the default topology name is found in gateway-site.xml as a property called: “default.app.topology.name”.</p><p>The default value for this property is “sandbox”.</p><p>Therefore, when deploying the sandbox.xml topology, both of the following example URLs work for the same underlying Hadoop cluster:</p>
+<pre><code>https://{gateway-host}:{gateway-port}/webhdfs
+https://{gateway-host}:{gateway-port}/{gateway-path}/{cluster-name}/webhdfs
+</code></pre><p>These default topology URLs exist for all of the services in the topology.</p><h4><a id="Fully+Qualified+URLs"></a>Fully Qualified URLs</h4><p>Examples of mappings for the WebHDFS, WebHCat, Oozie and Stargate/HBase are shown below. These mapping are generated from the combination of the gateway configuration file (i.e. <code>{GATEWAY_HOME}/conf/gateway-site.xml</code>) and the cluster topology descriptors (e.g. <code>{GATEWAY_HOME}/conf/topologies/{cluster-name}.xml</code>). The port numbers show for the Cluster URLs represent the default ports for these services. The actual port number may be different for a given cluster.</p>
+<ul>
+ <li>WebHDFS
+ <ul>
+ <li>Gateway: <code>https://{gateway-host}:{gateway-port}/{gateway-path}/{cluster-name}/webhdfs</code></li>
+ <li>Cluster: <code>http://{webhdfs-host}:50070/webhdfs</code></li>
+ </ul></li>
+ <li>WebHCat (Templeton)
+ <ul>
+ <li>Gateway: <code>https://{gateway-host}:{gateway-port}/{gateway-path}/{cluster-name}/templeton</code></li>
+ <li>Cluster: <code>http://{webhcat-host}:50111/templeton}</code></li>
+ </ul></li>
+ <li>Oozie
+ <ul>
+ <li>Gateway: <code>https://{gateway-host}:{gateway-port}/{gateway-path}/{cluster-name}/oozie</code></li>
+ <li>Cluster: <code>http://{oozie-host}:11000/oozie}</code></li>
+ </ul></li>
+ <li>Stargate (HBase)
+ <ul>
+ <li>Gateway: <code>https://{gateway-host}:{gateway-port}/{gateway-path}/{cluster-name}/hbase</code></li>
+ <li>Cluster: <code>http://{hbase-host}:60080</code></li>
+ </ul></li>
+ <li>Hive JDBC
+ <ul>
+ <li>Gateway: jdbc:hive2://{gateway-host}:{gateway-port}/;ssl=true;sslTrustStore={gateway-trust-store-path};trustStorePassword={gateway-trust-store-password}?hive.server2.transport.mode=http;hive.server2.thrift.http.path={gateway-path}/{cluster-name}/hive</li>
+ <li>Cluster: <code>http://{hive-host}:10001/cliservice</code></li>
+ </ul></li>
+</ul><p>The values for <code>{gateway-host}</code>, <code>{gateway-port}</code>, <code>{gateway-path}</code> are provided via the gateway configuration file (i.e. <code>{GATEWAY_HOME}/conf/gateway-site.xml</code>).</p><p>The value for <code>{cluster-name}</code> is derived from the file name of the cluster topology descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>The value for <code>{webhdfs-host}</code>, <code>{webhcat-host}</code>, <code>{oozie-host}</code>, <code>{hbase-host}</code> and <code>{hive-host}</code> are provided via the cluster topology descriptor (e.g. <code>{GATEWAY_HOME}/conf/topologies/{cluster-name}.xml</code>).</p><p>Note: The ports 50070, 50111, 11000, 60080 (default 8080) and 10001 are the defaults for WebHDFS, WebHCat, Oozie, Stargate/HBase and Hive respectively. Their values can also be provided via the cluster topology descriptor if your Hadoop cluster uses different ports.</p><h3><a id="Configuration"></a>Configuration</h
3><h3><a id="Related+Cluster+Configuration"></a>Related Cluster Configuration</h3><p>The following configuration changes must be made to your cluster to allow Apache Knox to dispatch requests to the various service components on behalf of end users.</p><h4><a id="Grant+Proxy+privileges+for+Knox+user+in+`core-site.xml`+on+Hadoop+master+nodes"></a>Grant Proxy privileges for Knox user in <code>core-site.xml</code> on Hadoop master nodes</h4><p>Update <code>core-site.xml</code> and add the following lines towards the end of the file.</p><p>Replace FQDN_OF_KNOX_HOST with the fully qualified domain name of the host running the gateway. You can usually find this by running <code>hostname -f</code> on that host.</p><p>You could use * for local developer testing if Knox host does not have static IP.</p>
+<pre><code><property>
+ <name>hadoop.proxyuser.knox.groups</name>
+ <value>users</value>
+</property>
+<property>
+ <name>hadoop.proxyuser.knox.hosts</name>
+ <value>FQDN_OF_KNOX_HOST</value>
+</property>
+</code></pre><h4><a id="Grant+proxy+privilege+for+Knox+in+`webhcat-site.xml`+on+Hadoop+master+nodes"></a>Grant proxy privilege for Knox in <code>webhcat-site.xml</code> on Hadoop master nodes</h4><p>Update <code>webhcat-site.xml</code> and add the following lines towards the end of the file.</p><p>Replace FQDN_OF_KNOX_HOST with right value in your cluster. You could use * for local developer testing if Knox host does not have static IP.</p>
+<pre><code><property>
+ <name>webhcat.proxyuser.knox.groups</name>
+ <value>users</value>
+</property>
+<property>
+ <name>webhcat.proxyuser.knox.hosts</name>
+ <value>FQDN_OF_KNOX_HOST</value>
+</property>
+</code></pre><h4><a id="Grant+proxy+privilege+for+Knox+in+`oozie-site.xml`+on+Oozie+host"></a>Grant proxy privilege for Knox in <code>oozie-site.xml</code> on Oozie host</h4><p>Update <code>oozie-site.xml</code> and add the following lines towards the end of the file.</p><p>Replace FQDN_OF_KNOX_HOST with right value in your cluster. You could use * for local developer testing if Knox host does not have static IP.</p>
+<pre><code><property>
+ <name>oozie.service.ProxyUserService.proxyuser.knox.groups</name>
+ <value>users</value>
+</property>
+<property>
+ <name>oozie.service.ProxyUserService.proxyuser.knox.hosts</name>
+ <value>FQDN_OF_KNOX_HOST</value>
+</property>
+</code></pre><h4><a id="Enable+http+transport+mode+and+use+substitution+in+Hive+Server2"></a>Enable http transport mode and use substitution in Hive Server2</h4><p>Update <code>hive-site.xml</code> and set the following properties on Hive Server2 hosts. Some of the properties may already be in the hive-site.xml. Ensure that the values match the ones below.</p>
+<pre><code><property>
+ <name>hive.server2.allow.user.substitution</name>
+ <value>true</value>
+</property>
+
+<property>
+ <name>hive.server2.transport.mode</name>
+ <value>http</value>
+ <description>Server transport mode. "binary" or "http".</description>
+</property>
+
+<property>
+ <name>hive.server2.thrift.http.port</name>
+ <value>10001</value>
+ <description>Port number when in HTTP mode.</description>
+</property>
+
+<property>
+ <name>hive.server2.thrift.http.path</name>
+ <value>cliservice</value>
+ <description>Path component of URL endpoint when in HTTP mode.</description>
+</property>
+</code></pre><h4><a id="Topology+Descriptors"></a>Topology Descriptors</h4><p>The topology descriptor files provide the gateway with per-cluster configuration information. This includes configuration for both the providers within the gateway and the services within the Hadoop cluster. These files are located in <code>{GATEWAY_HOME}/conf/topologies</code>. The general outline of this document looks like this.</p>
+<pre><code><topology>
+ <gateway>
+ <provider>
+ </provider>
+ </gateway>
+ <service>
+ </service>
+</topology>
+</code></pre><p>There are typically multiple <code><provider></code> and <code><service></code> elements.</p>
+<dl><dt>/topology</dt><dd>Defines the provider and configuration and service topology for a single Hadoop cluster.</dd><dt>/topology/gateway</dt><dd>Groups all of the provider elements</dd><dt>/topology/gateway/provider</dt><dd>Defines the configuration of a specific provider for the cluster.</dd><dt>/topology/service</dt><dd>Defines the location of a specific Hadoop service within the Hadoop cluster.</dd>
+</dl><h5><a id="Provider+Configuration"></a>Provider Configuration</h5><p>Provider configuration is used to customize the behavior of a particular gateway feature. The general outline of a provider element looks like this.</p>
+<pre><code><provider>
+ <role>authentication</role>
+ <name>ShiroProvider</name>
+ <enabled>true</enabled>
+ <param>
+ <name></name>
+ <value></value>
+ </param>
+</provider>
+</code></pre>
+<dl><dt>/topology/gateway/provider</dt><dd>Groups information for a specific provider.</dd><dt>/topology/gateway/provider/role</dt><dd>Defines the role of a particular provider. There are a number of pre-defined roles used by out-of-the-box provider plugins for the gateay. These roles are: authentication, identity-assertion, authentication, rewrite and hostmap</dd><dt>/topology/gateway/provider/name</dt><dd>Defines the name of the provider for which this configuration applies. There can be multiple provider implementations for a given role. Specifying the name is used identify which particular provider is being configured. Typically each topology descriptor should contain only one provider for each role but there are exceptions.</dd><dt>/topology/gateway/provider/enabled</dt><dd>Allows a particular provider to be enabled or disabled via <code>true</code> or <code>false</code> respectively. When a provider is disabled any filters associated with that provider are excluded from the pr
ocessing chain.</dd><dt>/topology/gateway/provider/param</dt><dd>These elements are used to supply provider configuration. There can be zero or more of these per provider.</dd><dt>/topology/gateway/provider/param/name</dt><dd>The name of a parameter to pass to the provider.</dd><dt>/topology/gateway/provider/param/value</dt><dd>The value of a parameter to pass to the provider.</dd>
+</dl><h5><a id="Service+Configuration"></a>Service Configuration</h5><p>Service configuration is used to specify the location of services within the Hadoop cluster. The general outline of a service element looks like this.</p>
+<pre><code><service>
+ <role>WEBHDFS</role>
+ <url>http://localhost:50070/webhdfs</url>
+</service>
+</code></pre>
+<dl><dt>/topology/service</dt><dd>Provider information about a particular service within the Hadoop cluster. Not all services are necessarily exposed as gateway endpoints.</dd><dt>/topology/service/role</dt><dd>Identifies the role of this service. Currently supported roles are: WEBHDFS, WEBHCAT, WEBHBASE, OOZIE, HIVE, NAMENODE, JOBTRACKER, RESOURCEMANAGER Additional service roles can be supported via plugins.</dd><dt>topology/service/url</dt><dd>The URL identifying the location of a particular service within the Hadoop cluster.</dd>
+</dl><h4><a id="Hostmap+Provider"></a>Hostmap Provider</h4><p>The purpose of the Hostmap provider is to handle situations where host are known by one name within the cluster and another name externally. This frequently occurs when virtual machines are used and in particular when using cloud hosting services. Currently, the Hostmap provider is configured as part of the topology file. The basic structure is shown below.</p>
+<pre><code><topology>
+ <gateway>
+ ...
+ <provider>
+ <role>hostmap</role>
+ <name>static</name>
+ <enabled>true</enabled>
+ <param><name>external-host-name</name><value>internal-host-name</value></param>
+ </provider>
+ ...
+ </gateway>
+ ...
+</topology>
+</code></pre><p>This mapping is required because the Hadoop servies running within the cluster are unaware that they are being accessed from outside the cluster. Therefore URLs returned as part of REST API responses will typically contain internal host names. Since clients outside the cluster will be unable to resolve those host name they must be mapped to external host names.</p><h5><a id="Hostmap+Provider+Example+-+EC2"></a>Hostmap Provider Example - EC2</h5><p>Consider an EC2 example where two VMs have been allocated. Each VM has an external host name by which it can be accessed via the internet. However the EC2 VM is unaware of this external host name and instead is configured with the internal host name.</p>
+<pre><code>External HOSTNAMES:
+ec2-23-22-31-165.compute-1.amazonaws.com
+ec2-23-23-25-10.compute-1.amazonaws.com
+
+Internal HOSTNAMES:
+ip-10-118-99-172.ec2.internal
+ip-10-39-107-209.ec2.internal
+</code></pre><p>The Hostmap configuration required to allow access external to the Hadoop cluster via the Apache Knox Gateway would be this.</p>
+<pre><code><topology>
+ <gateway>
+ ...
+ <provider>
+ <role>hostmap</role>
+ <name>static</name>
+ <enabled>true</enabled>
+ <param>
+ <name>ec2-23-22-31-165.compute-1.amazonaws.com</name>
+ <value>ip-10-118-99-172.ec2.internal</value>
+ </param>
+ <param>
+ <name>ec2-23-23-25-10.compute-1.amazonaws.com</name>
+ <value>ip-10-39-107-209.ec2.internal</value>
+ </param>
+ </provider>
+ ...
+ </gateway>
+ ...
+</topology>
+</code></pre><h5><a id="Hostmap+Provider+Example+-+Sandbox"></a>Hostmap Provider Example - Sandbox</h5><p>The Hortonworks Sandbox 2.x poses a different challenge for host name mapping. This version of the Sandbox uses port mapping to make the Sandbox VM appear as though it is accessible via localhost. However the Sandbox VM is internally configured to consider sandbox.hortonworks.com as the host name. So from the perspective of a client accessing Sandbox the external host name is localhost. The Hostmap configuration required to allow access to Sandbox from the host operating system is this.</p>
+<pre><code><topology>
+ <gateway>
+ ...
+ <provider>
+ <role>hostmap</role>
+ <name>static</name>
+ <enabled>true</enabled>
+ <param><name>localhost</name><value>sandbox,sandbox.hortonworks.com</value></param>
+ </provider>
+ ...
+ </gateway>
+ ...
+</topology>
+</code></pre><h5><a id="Hostmap+Provider+Configuration"></a>Hostmap Provider Configuration</h5><p>Details about each provider configuration element is enumerated below.</p>
+<dl><dt>topology/gateway/provider/role</dt><dd>The role for a Hostmap provider must always be <code>hostmap</code>.</dd><dt>topology/gateway/provider/name</dt><dd>The Hostmap provider supplied out-of-the-box is selected via the name <code>static</code>.</dd><dt>topology/gateway/provider/enabled</dt><dd>Host mapping can be enabled or disabled by providing <code>true</code> or <code>false</code>.</dd><dt>topology/gateway/provider/param</dt><dd>Host mapping is configured by providing parameters for each external to internal mapping.</dd><dt>topology/gateway/provider/param/name</dt><dd>The parameter names represent an external host names associated with the internal host names provided by the value element. This can be a comma separated list of host names that all represent the same physical host. When mapping from internal to external host name the first external host name in the list is used.</dd><dt>topology/gateway/provider/param/value</dt><dd>The parameter values represent the inte
rnal host names associated with the external host names provider by the name element. This can be a comma separated list of host names that all represent the same physical host. When mapping from external to internal host names the first internal host name in the list is used.</dd>
+</dl><h4><a id="Logging"></a>Logging</h4><p>If necessary you can enable additional logging by editing the <code>log4j.properties</code> file in the <code>conf</code> directory. Changing the rootLogger value from <code>ERROR</code> to <code>DEBUG</code> will generate a large amount of debug logging. A number of useful, more fine loggers are also provided in the file.</p><h4><a id="Java+VM+Options"></a>Java VM Options</h4><p>TODO - Java VM options doc.</p><h4><a id="Persisting+the+Master+Secret"></a>Persisting the Master Secret</h4><p>The master secret is required to start the server. This secret is used to access secured artifacts by the gateway instance. Keystore, trust stores and credential stores are all protected with the master secret.</p><p>You may persist the master secret by supplying the <em>-persist-master</em> switch at startup. This will result in a warning indicating that persisting the secret is less secure than providing it at startup. We do make some provisions in ord
er to protect the persisted password.</p><p>It is encrypted with AES 128 bit encryption and where possible the file permissions are set to only be accessible by the user that the gateway is running as.</p><p>After persisting the secret, ensure that the file at config/security/master has the appropriate permissions set for your environment. This is probably the most important layer of defense for master secret. Do not assume that the encryption if sufficient protection.</p><p>A specific user should be created to run the gateway this user will be the only user with permissions for the persisted master file.</p><p>See the Knox CLI section for descriptions of the command line utilties related to the master secret.</p><h4><a id="Management+of+Security+Artifacts"></a>Management of Security Artifacts</h4><p>There are a number of artifacts that are used by the gateway in ensuring the security of wire level communications, access to protected resources and the encryption of sensitive data. T
hese artifacts can be managed from outside of the gateway instances or generated and populated by the gateway instance itself.</p><p>The following is a description of how this is coordinated with both standalone (development, demo, etc) gateway instances and instances as part of a cluster of gateways in mind.</p><p>Upon start of the gateway server we:</p>
+<ol>
+ <li>Look for an identity store at <code>data/security/keystores/gateway.jks</code>. The identity store contains the certificate and private key used to represent the identity of the server for SSL connections and signature creation.
+ <ul>
+ <li>If there is no identity store we create one and generate a self-signed certificate for use in standalone/demo mode. The certificate is stored with an alias of gateway-identity.</li>
+ <li>If there is an identity store found than we ensure that it can be loaded using the provided master secret and that there is an alias called gateway-identity.</li>
+ </ul></li>
+ <li>Look for a credential store at <code>data/security/keystores/__gateway-credentials.jceks</code>. This credential store is used to store secrets/passwords that are used by the gateway. For instance, this is where the passphrase for accessing the gateway-identity certificate is kept.
+ <ul>
+ <li>If there is no credential store found then we create one and populate it with a generated passphrase for the alias <code>gateway-identity-passphrase</code>. This is coordinated with the population of the self-signed cert into the identity-store.</li>
+ <li>If a credential store is found then we ensure that it can be loaded using the provided master secret and that the expected aliases have been populated with secrets.</li>
+ </ul></li>
+</ol><p>Upon deployment of a Hadoop cluster topology within the gateway we:</p>
+<ol>
+ <li>Look for a credential store for the topology. For instance, we have a sample topology that gets deployed out of the box. We look for <code>data/security/keystores/sandbox-credentials.jceks</code>. This topology specific credential store is used for storing secrets/passwords that are used for encrypting sensitive data with topology specific keys.
+ <ul>
+ <li>If no credential store is found for the topology being deployed then one is created for it. Population of the aliases is delegated to the configured providers within the system that will require the use of a secret for a particular task. They may programmatic set the value of the secret or choose to have the value for the specified alias generated through the AliasService.</li>
+ <li>If a credential store is found then we ensure that it can be loaded with the provided master secret and the configured providers have the opportunity to ensure that the aliases are populated and if not to populate them.</li>
+ </ul></li>
+</ol><p>By leveraging the algorithm described above we can provide a window of opportunity for management of these artifacts in a number of ways.</p>
+<ol>
+ <li>Using a single gateway instance as a master instance the artifacts can be generated or placed into the expected location and then replicated across all of the slave instances before startup.</li>
+ <li>Using an NFS mount as a central location for the artifacts would provide a single source of truth without the need to replicate them over the network. Of course, NFS mounts have their own challenges.</li>
+ <li>Using the KnoxCLI to create and manage the security artifacts.</li>
+</ol><p>See the Knox CLI section for descriptions of the command line utilties related to the security artifact management.</p><h4><a id="Keystores"></a>Keystores</h4><p>In order to provide your own certificate for use by the gateway, you will need to either import an existing key pair into a Java keystore or generate a self-signed cert using the Java keytool.</p><h5><a id="Importing+a+key+pair+into+a+Java+keystore"></a>Importing a key pair into a Java keystore</h5><p>One way to accomplish this is to start with a PKCS12 store for your key pair and then convert it to a Java keystore or JKS.</p><p>The following example uses openssl to create a PKCS12 encoded store from your provided certificate and private key that are in PEM format.</p>
+<pre><code>openssl pkcs12 -export -in cert.pem -inkey key.pem > server.p12
+</code></pre><p>The next example converts the PKCS12 store into a Java keystore (JKS). It should prompt you for the keystore and key passwords for the destination keystore. You must use the master-secret for the keystore password and keep track of the password that you use for the key passphrase.</p>
+<pre><code>keytool -importkeystore -srckeystore {server.p12} -destkeystore gateway.jks -srcstoretype pkcs12
+</code></pre><p>While using this approach a couple of important things to be aware of:</p>
+<ol>
+ <li><p>the alias MUST be “gateway-identity”. You may need to change it using keytool after the import of the PKCS12 store. You can use keytool to do this - for example:</p><p>keytool -changealias -alias “1” -destalias “gateway-identity” -keystore gateway.jks -storepass {knoxpw}</p></li>
+ <li><p>the name of the expected identity keystore for the gateway MUST be gateway.jks</p></li>
+ <li><p>the passwords for the keystore and the imported key may both be set to the master secret for the gateway install. You can change the key passphrase after import using keytool as well. You may need to do this in order to provision the password in the credential store as described later in this section. For example:</p><p>keytool -keypasswd -alias gateway-identity -keystore gateway.jks</p></li>
+</ol><p>NOTE: The password for the keystore as well as that of the imported key may be the master secret for the gateway instance or you may set the gateway-identity-passphrase alias using the Knox CLI to the actual key passphrase. See the Knox CLI section for details.</p><p>The following will allow you to provision the passphrase for the private key that you set during keystore creation above - it will prompt you for the actual passphrase.</p>
+<pre><code>bin/knoxcli.sh create-alias gateway-identity-passphrase
+</code></pre><h5><a id="Generating+a+self-signed+cert+for+use+in+testing+or+development+environments"></a>Generating a self-signed cert for use in testing or development environments</h5>
+<pre><code>keytool -genkey -keyalg RSA -alias gateway-identity -keystore gateway.jks \
+ -storepass {master-secret} -validity 360 -keysize 2048
+</code></pre><p>Keytool will prompt you for a number of elements used will comprise the distiniguished name (DN) within your certificate. </p><p><em>NOTE:</em> When it prompts you for your First and Last name be sure to type in the hostname of the machine that your gateway instance will be running on. This is used by clients during hostname verification to ensure that the presented certificate matches the hostname that was used in the URL for the connection - so they need to match.</p><p><em>NOTE:</em> When it prompts for the key password just press enter to ensure that it is the same as the keystore password. Which, as was described earlier, must match the master secret for the gateway instance. Alternatively, you can set it to another passphrase - take note of it and set the gateway-identity-passphrase alias to that passphrase using the Knox CLI.</p><p>See the Knox CLI section for descriptions of the command line utilties related to the management of the keystores.</p><h5><a id="U
sing+a+CA+Signed+Key+Pair"></a>Using a CA Signed Key Pair</h5><p>For certain deployments a certificate key pair that is signed by a trusted certificate authority is required. There are a number of different ways in which these certificates are acquired and can be converted and imported into the Apache Knox keystore.</p><p>The following steps have been used to do this and are provided here for guidance in your installation. You may have to adjust according to your environment.</p><p>General steps:</p>
+<ol>
+ <li>stop gateway and back up all files in /var/lib/knox/data/security/keystores<br/>gateway.sh stop</li>
+ <li>create new master key for knox and persist, the master key will be referred to in following steps as $master-key<br/>knoxcli.sh create-master -force</li>
+ <li>create identity keystore gateway.jks. cert in alias gateway-identity
+ <ul>
+ <li>cd /var/lib/knox/data/security/keystore</li>
+ <li>keytool -genkeypair -alias gateway-identity -keyalg RSA -keysize 1024 -dname “CN=$fqdn_knox,OU=hdp,O=sdge” -keypass $keypass -keystore gateway.jks -storepass $master-key -validity 300<br/>NOTE: above $fqdn_knox is the hostname of the knox host. adjust validity as needed. some may choose $keypass to be the same as $master-key</li>
+ </ul></li>
+ <li>create credential store to store the $keypass in step 3. this creates __gateway-credentials.jceks file<br/>
+ <ul>
+ <li>knoxcli.sh create-alias gateway-identity-passphrase –value $keypass</li>
+ </ul></li>
+ <li>generate a certificate signing request from the gateway.jks
+ <ul>
+ <li>keytool -keystore gateway.jks -storepass $master-key -alias gateway-identity -certreq -file knox.csr</li>
+ </ul></li>
+ <li>send the knox.csr file to the CA authority and get back the singed certificate, signed cert referred to as knox.signed in following steps. Also need the CA cert, which normally can be requested through openssl command or web browser. (or can ask the CA authority to send a copy).</li>
+ <li>import both the CA authority certificate (referred as corporateCA.cer) and the signed knox certificate back into gateway.jks
+ <ul>
+ <li>keytool -keystore gateway.jks -storepass $master-key -alias $hwhq -import -file corporateCA.cer</li>
+ <li>keytool -keystore gateway.jks -storepass $master-key -alias gateway-identity -import -file knox.signed<br/>Note: use any alias appropriate for the corporate CA.</li>
+ </ul></li>
+ <li>restart gateway. check gateway.log to see that gateway started properly and clusters are deployed. Can check the timestamp on cluster deployment files
+ <ul>
+ <li>ls -alrt /var/lib/knox/data/deployment</li>
+ </ul></li>
+ <li>verify that clients can use the CA authority cert to access Knox (which is the goal of using public signed cert)
+ <ul>
+ <li>curl –cacert supwin12ad.cer -u hdptester:hadoop -X GET ‘<a href="https://$fqdn_knox:8443/gateway/$topologyname/webhdfs/v1/tmp?op=LISTSTATUS">https://$fqdn_knox:8443/gateway/$topologyname/webhdfs/v1/tmp?op=LISTSTATUS</a>’ or can verify through client browser which already has the corporate CA cert installed.</li>
+ </ul></li>
+</ol><h5><a id="Credential+Store"></a>Credential Store</h5><p>Whenever you provide your own keystore with either a self-signed cert or an issued certificate signed by a trusted authority, you will need to set an alias for the gateway-identity-passphrase or create an empty credential store. This is necessary for the current release in order for the system to determine the correct password for the keystore and the key.</p><p>The credential stores in Knox use the JCEKS keystore type as it allows for the storage of general secrets in addition to certificates.</p><p>Keytool may be used to create credential stores but the Knox CLI section details how to create aliases. These aliases are managed within credential stores which are created by the CLI as needed. The simplest approach is to create the gateway-identity-passpharse alias with the Knox CLI. This will create the credential store if it doesn’t already exist and add the key passphrase.</p><p>See the Knox CLI section for descrip
tions of the command line utilties related to the management of the credential stores.</p><h5><a id="Provisioning+of+Keystores"></a>Provisioning of Keystores</h5><p>Once you have created these keystores you must move them into place for the gateway to discover them and use them to represent its identity for SSL connections. This is done by copying the keystores to the <code>{GATEWAY_HOME}/data/security/keystores</code> directory for your gateway install.</p><h4><a id="Summary+of+Secrets+to+be+Managed"></a>Summary of Secrets to be Managed</h4>
+<ol>
+ <li>Master secret - the same for all gateway instances in a cluster of gateways</li>
+ <li>All security related artifacts are protected with the master secret</li>
+ <li>Secrets used by the gateway itself are stored within the gateway credential store and are the same across all gateway instances in the cluster of gateways</li>
+ <li>Secrets used by providers within cluster topologies are stored in topology specific credential stores and are the same for the same topology across the cluster of gateway instances. However, they are specific to the topology - so secrets for one hadoop cluster are different from those of another. This allows for fail-over from one gateway instance to another even when encryption is being used while not allowing the compromise of one encryption key to expose the data for all clusters.</li>
+</ol><p>NOTE: the SSL certificate will need special consideration depending on the type of certificate. Wildcard certs may be able to be shared across all gateway instances in a cluster. When certs are dedicated to specific machines the gateway identity store will not be able to be blindly replicated as host name verification problems will ensue. Obviously, trust-stores will need to be taken into account as well.</p><h3><a id="Knox+CLI"></a>Knox CLI</h3><p>The Knox CLI is a command line utility for management of various aspects of the Knox deployment. It is primarily concerned with the management of the security artifacts for the gateway instance and each of the deployed topologies or hadoop clusters that are gated by the Knox Gateway instance.</p><p>The various security artifacts are also generated and populated automatically by the Knox Gateway runtime when they are not found at startup. The assumptions made in those cases are appropriate for a test or development gateway instance
and assume ‘localhost’ for hostname specific activities. For production deployments the use of the CLI may aid in managing some production deployments.</p><p>The knoxcli.sh script is located in the {GATEWAY_HOME}/bin directory.</p><h4><a id="Help"></a>Help</h4><h5><a id="`bin/knoxcli.sh+[--help]`"></a><code>bin/knoxcli.sh [--help]</code></h5><p>prints help for all commands</p><h4><a id="Knox+Verison+Info"></a>Knox Verison Info</h4><h5><a id="`bin/knoxcli.sh+version+[--help]`"></a><code>bin/knoxcli.sh version [--help]</code></h5><p>Displays Knox version information.</p><h4><a id="Master+secret+persistence"></a>Master secret persistence</h4><h5><a id="`bin/knoxcli.sh+create-master+[--force][--help]`"></a><code>bin/knoxcli.sh create-master [--force][--help]</code></h5><p>Creates and persists an encrypted master secret in a file within {GATEWAY_HOME}/data/security/master. </p><p>NOTE: This command fails when there is an existing master file in the expected location. You may
force it to overwrite the master file with the --force switch. NOTE: this will require you to change passwords protecting the keystores for the gateway identity keystores and all credential stores.</p><h4><a id="Alias+creation"></a>Alias creation</h4><h5><a id="`bin/knoxcli.sh+create-alias+name+[--cluster+c]+[--value+v]+[--generate]+[--help]`"></a><code>bin/knoxcli.sh create-alias name [--cluster c] [--value v] [--generate] [--help]</code></h5><p>Creates a password alias and stores it in a credential store within the {GATEWAY_HOME}/data/security/keystores dir. </p>
+<table>
+ <thead>
+ <tr>
+ <th>argument </th>
+ <th>description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>name</td>
+ <td>name of the alias to create</td>
+ </tr>
+ <tr>
+ <td>--cluster</td>
+ <td>name of Hadoop cluster for the cluster specific credential store otherwise assumes that it is for the gateway itself</td>
+ </tr>
+ <tr>
+ <td>--value</td>
+ <td>parameter for specifying the actual password otherwise prompted. Escape complex passwords or surround with single quotes.<br/></td>
+ </tr>
+ <tr>
+ <td>--generate</td>
+ <td>boolean flag to indicate whether the tool should just generate the value. This assumes that --value is not set - will result in error otherwise. User will not be prompted for the value when --generate is set.</td>
+ </tr>
+ </tbody>
+</table><h4><a id="Alias+deletion"></a>Alias deletion</h4><h5><a id="`bin/knoxcli.sh+delete-alias+name+[--cluster+c]+[--help]`"></a><code>bin/knoxcli.sh delete-alias name [--cluster c] [--help]</code></h5><p>Deletes a password and alias mapping from a credential store within {GATEWAY_HOME}/data/security/keystores. </p>
+<table>
+ <thead>
+ <tr>
+ <th>argument </th>
+ <th>description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>name </td>
+ <td>name of the alias to delete</td>
+ </tr>
+ <tr>
+ <td>--cluster </td>
+ <td>name of Hadoop cluster for the cluster specific credential store otherwise assumes ’__gateway’</td>
+ </tr>
+ </tbody>
+</table><h4><a id="Alias+listing"></a>Alias listing</h4><h5><a id="`bin/knoxcli.sh+list-alias+[--cluster+c]+[--help]`"></a><code>bin/knoxcli.sh list-alias [--cluster c] [--help]</code></h5><p>Lists the alias names for the credential store within {GATEWAY_HOME}/data/security/keystores. </p><p>NOTE: This command will list the aliases in lowercase which is a result of the underlying credential store implementation. Lookup of credentials is a case insensitive operation - so this is not an issue.</p>
+<table>
+ <thead>
+ <tr>
+ <th>argument </th>
+ <th>description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>--cluster </td>
+ <td>name of Hadoop cluster for the cluster specific credential store otherwise assumes ’__gateway’</td>
+ </tr>
+ </tbody>
+</table><h4><a id="Self-signed+cert+creation"></a>Self-signed cert creation</h4><h5><a id="`bin/knoxcli.sh+create-cert+[--hostname+n]+[--help]`"></a><code>bin/knoxcli.sh create-cert [--hostname n] [--help]</code></h5><p>Creates and stores a self-signed certificate to represent the identity of the gateway instance. This is stored within the {GATEWAY_HOME}/data/security/keystores/gateway.jks keystore. </p>
+<table>
+ <thead>
+ <tr>
+ <th>argument </th>
+ <th>description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>--hostname</td>
+ <td>name of the host to be used in the self-signed certificate. This allows multi-host deployments to specify the proper hostnames for hostname verification to succeed on the client side of the SSL connection. The default is ‘localhost’.</td>
+ </tr>
+ </tbody>
+</table><h4><a id="Topology+Redeploy"></a>Topology Redeploy</h4><h5><a id="`bin/knoxcli.sh+redeploy+[--cluster+c]`"></a><code>bin/knoxcli.sh redeploy [--cluster c]</code></h5><p>Redeploys one or all of the gateway’s clusters (a.k.a topologies).</p><h3><a id="Admin+API"></a>Admin API</h3><p>Access to the administrator functions of Knox are provided by the Admin REST API.</p><h4><a id="Admin+API+URL"></a>Admin API URL</h4><p>The URL mapping for the Knox Admin API is simple:</p>
+<table>
+ <tbody>
+ <tr>
+ <td>Gateway </td>
+ <td><code>https://{gateway-host}:{gateway-port}/{gateway-path}/admin/api/v1</code> </td>
+ </tr>
+ </tbody>
+</table><p>Please note that to access that admin API, the user attempting to connect must have admin credentials inside of the LDAP Server</p><h5><a id="API+Documentation"></a>API Documentation</h5><h6><a id="Operations"></a>Operations</h6>
+<ul>
+ <li><h6>HTTP GET</h6> 1. <a href="#Server+Version">Server Version</a><br/> 2. <a href="#Topology+Collection">Topology Collection</a><br/> 3. <a href="#Topology">Topology</a></li>
+ <li><h6>HTTP PUT</h6></li>
+ <li><h6>HTTP DELETE</h6></li>
+</ul><h5><a id="Server+Version"></a>Server Version</h5><h6><a id="Description"></a>Description</h6><p>Calls to Knox and returns the gateway’s current version and the version hash inside of a JSON object. </p><h6><a id="Example+Request+URL"></a>Example Request URL</h6><p><code>https://{gateway-host}:{gateway-port}/{gateway-path}/admin/api/v1/version</code> </p><h6><a id="Example+cURL+Request"></a>Example cURL Request</h6><p><code>curl -u admin:admin-password -i -k https://{gateway-host}:{gateway-port}/{gateway-path}/admin/api/v1/version</code></p><h6><a id="Response"></a>Response</h6>
+<pre><code> <ServerVersion>
+ <version>0.6.0</version>
+ <hash>{version-hash}</hash>
+ </ServerVersion>
+</code></pre><h5><a id="Topology+Collection"></a>Topology Collection</h5><h6><a id="Description"></a>Description</h6><p>Calls to Knox and return an array of JSON objects that represent the list of deployed topologies currently inside of the gateway. </p><h6><a id="Example+Request+URL"></a>Example Request URL</h6><p><code>https://{gateway-host}:{gateway-port}/{gateway-path}/admin/api/{api-version}/topologies</code> </p><h6><a id="Example+cURL+Request"></a>Example cURL Request</h6><p><code>curl -u admin:admin-password -i -k -H Accept:application/json https://{gateway-host}:{gateway-port}/{gateway-path}/admin/api/v1/topologies</code></p><h6><a id="Response"></a>Response</h6>
+<pre><code>[
+ {
+ "href":"https://localhost:8443/gateway/admin/api/v1/topologies/_default",
+ "name":"_default",
+ "timestamp":"1405633120000",
+ "uri":"https://localhost:8443/gateway/_default"
+ },
+ {
+ "href":"https://localhost:8443/gateway/admin/api/v1/topologies/admin",
+ "name":"admin",
+ "timestamp":"1406672646000",
+ "uri":"https://localhost:8443/gateway/admin"
+ }
+]
+</code></pre><h5><a id="Topology"></a>Topology</h5><h6><a id="Description"></a>Description</h6><p>Calls to Knox and return a JSON object that represents the requested topology </p><h6><a id="Example+Request+URL"></a>Example Request URL</h6><p><code>https://{gateway-host}:{gateway-port}/{gateway-path}/admin/api/v1/topologies/{topology-name}</code> </p><h6><a id="Example+cURL+Request"></a>Example cURL Request</h6><p><code>curl -u admin:admin-password -i -k -H Accept:application/json https://{gateway-host}:{gateway-port}/{gateway-path}/admin/api/v1/topologies/{topology-name}</code></p><h6><a id="Response"></a>Response</h6>
+<pre><code>{
+ "name": "admin",
+ "providers": [{
+ "enabled": true,
+ "name": "ShiroProvider",
+ "params": {
+ "sessionTimeout": "30",
+ "main.ldapRealm": "org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm",
+ "main.ldapRealm.userDnTemplate": "uid={0},ou=people,dc=hadoop,dc=apache,dc=org",
+ "main.ldapRealm.contextFactory.url": "ldap://localhost:33389",
+ "main.ldapRealm.contextFactory.authenticationMechanism": "simple",
+ "urls./**": "authcBasic"
+ },
+ "role": "authentication"
+ }, {
+ "enabled": true,
+ "name": "AclsAuthz",
+ "params": {
+ "knox.acl": "admin;*;*"
+ },
+ "role": "authorization"
+ }, {
+ "enabled": true,
+ "name": "Default",
+ "params": {},
+ "role": "identity-assertion"
+ }, {
+ "enabled": true,
+ "name": "static",
+ "params": {
+ "localhost": "sandbox,sandbox.hortonworks.com"
+ },
+ "role": "hostmap"
+ }],
+ "services": [{
+ "name": null,
+ "params": {},
+ "role": "KNOX",
+ "url": null
+ }],
+ "timestamp": 1406672646000,
+ "uri": "https://localhost:8443/gateway/admin"
+}
+</code></pre><h3><a id="X-Forwareded-*+Headers+Support"></a>X-Forwareded-* Headers Support</h3><p>Out-of-the-box Knox provides support for some X-Forwarded-* headers through the use of a Servlet Filter. Specifically the headers handled/populated by Knox are:</p>
+<ul>
+ <li>X-Forwarded-For</li>
+ <li>X-Forwarded-Proto</li>
+ <li>X-Forwarded-Port</li>
+ <li>X-Forwarded-Host</li>
+ <li>X-Forwarded-Server</li>
+ <li>X-Forwarded-Context</li>
+</ul><p>If this functionality can be turned off by a configuration setting in the file gateway-site.xml and redeploying the necessary topology/topologies.</p><p>The setting is (under the ‘configuration’ tag) :</p>
+<pre><code> <property>
+ <name>gateway.xforwarded.enabled</name>
+ <value>false</value>
+ </property>
+</code></pre><p>If this setting is absent, the default behavior is that the X-Forwarded-* header support is on or in other words, ‘gateway.xforwarded.enabled’ is set to ‘true’ by default.</p><h4><a id="Header+population"></a>Header population</h4><p>The following are the various rules for population of these headers:</p><h5><a id="X-Forwarded-For"></a>X-Forwarded-For</h5><p>This header represents a list of client IP addresses. If the header is already present Knox adds a comma separated value to the list. The value added is the client’s IP address as Knox sees it. This value is added to the end of the list.</p><h5><a id="X-Forwarded-Proto"></a>X-Forwarded-Proto</h5><p>The protocol used in the client request. If this header is passed into Knox it’s value is maintained, otherwise Knox will populate the header with the value ‘https’ if the request is a secure one or ‘http’ otherwise.</p><h5><a id="X-Forwarded-Port"></a>X-Forwa
rded-Port</h5><p>The port used in the client request. If this header is passed into Knox it’s value is maintained, otherwise Knox will populate the header with the value of the port that the request was made coming into Knox.</p><h5><a id="X-Forwarded-Host"></a>X-Forwarded-Host</h5><p>Represents the original host requested by the client in the Host HTTP request header. The value passed into Knox is maintained by Knox. If no value is present, Knox populates the header with the value of the HTTP Host header.</p><h5><a id="X-Forwarded-Server"></a>X-Forwarded-Server</h5><p>The hostname of the server Knox is running on.</p><h5><a id="X-Forwarded-Context"></a>X-Forwarded-Context</h5><p>This header value contains the context path of the request to Knox.</p><h3><a id="Authentication"></a>Authentication</h3><p>There are two types of providers supported in Knox for establishing a user’s identity:</p>
+<ol>
+ <li>Authentication Providers</li>
+ <li>Federation Providers</li>
+</ol><p>Authentication providers directly accept a user’s credentials and validates them against some particular user store. Federation providers, on the other hand, validate a token that has been issued for the user by a trusted Identity Provider (IdP).</p><p>The current release of Knox ships with an authentication provider based on the Apache Shiro project and is initially configured for BASIC authentication against an LDAP store. This has been specifically tested against Apache Directory Server and Active Directory.</p><p>This section will cover the general approach to leveraging Shiro within the bundled provider including:</p>
+<ol>
+ <li>General mapping of provider config to shiro.ini config</li>
+ <li>Specific configuration for the bundled BASIC/LDAP configuration</li>
+ <li>Some tips into what may need to be customized for your environment</li>
+ <li>How to setup the use of LDAP over SSL or LDAPS</li>
+</ol><h4><a id="General+Configuration+for+Shiro+Provider"></a>General Configuration for Shiro Provider</h4><p>As is described in the configuration section of this document, providers have a name-value based configuration - as is the common pattern in the rest of Hadoop.</p><p>The following example shows the format of the configuration for a given provider:</p>
+<pre><code><provider>
+ <role>authentication</role>
+ <name>ShiroProvider</name>
+ <enabled>true</enabled>
+ <param>
+ <name>{name}</name>
+ <value>{value}</value>
+ </param>
+</provider>
+</code></pre><p>Conversely, the Shiro provider currently expects a shiro.ini file in the web-inf directory of the cluster specific web application.</p><p>The following example illustrates a configuration of the bundled BASIC/LDAP authentication config in a shiro.ini file:</p>
+<pre><code>[urls]
+/**=authcBasic
+[main]
+ldapRealm=org.apache.shiro.realm.ldap.JndiLdapRealm
+ldapRealm.contextFactory.authenticationMechanism=simple
+ldapRealm.contextFactory.url=ldap://localhost:33389
+ldapRealm.userDnTemplate=uid={0},ou=people,dc=hadoop,dc=apache,dc=org
+</code></pre><p>In order to fit into the context of an INI file format, at deployment time we interrogate the parameters provided in the provider configuration and parse the INI section out of the parameter names. The following provider config illustrates this approach. Notice that the section names in the above shiro.ini match the beginning of the param names that are in the following config:</p>
+<pre><code><gateway>
+ <provider>
+ <role>authentication</role>
+ <name>ShiroProvider</name>
+ <enabled>true</enabled>
+ <param>
+ <name>main.ldapRealm</name>
+ <value>org.apache.shiro.realm.ldap.JndiLdapRealm</value>
+ </param>
+ <param>
+ <name>main.ldapRealm.userDnTemplate</name>
+ <value>uid={0},ou=people,dc=hadoop,dc=apache,dc=org</value>
+ </param>
+ <param>
+ <name>main.ldapRealm.contextFactory.url</name>
+ <value>ldap://localhost:33389</value>
+ </param>
+ <param>
+ <name>main.ldapRealm.contextFactory.authenticationMechanism</name>
+ <value>simple</value>
+ </param>
+ <param>
+ <name>urls./**</name>
+ <value>authcBasic</value>
+ </param>
+ </provider>
+</code></pre><p>This happens to be the way that we are currently configuring Shiro for BASIC/LDAP authentication. This same config approach may be used to achieve other authentication mechanisms or variations on this one. We however have not tested additional uses for it for this release.</p><h4><a id="LDAP+Configuration"></a>LDAP Configuration</h4><p>This section discusses the LDAP configuration used above for the Shiro Provider. Some of these configuration elements will need to be customized to reflect your deployment environment.</p><p><strong>main.ldapRealm</strong> - this element indicates the fully qualified classname of the Shiro realm to be used in authenticating the user. The classname provided by default in the sample is the <code>org.apache.shiro.realm.ldap.JndiLdapRealm</code> this implementation provides us with the ability to authenticate but by default has authorization disabled. In order to provide authorization - which is seen by Shiro as dependent on an LDAP schema
that is specific to each organization - an extension of JndiLdapRealm is generally used to override and implement the doGetAuhtorizationInfo method. In this particular release we are providing a simple authorization provider that can be used along with the Shiro authentication provider.</p><p><strong>main.ldapRealm.userDnTemplate</strong> - in order to bind a simple username to an LDAP server that generally requires a full distinguished name (DN), we must provide the template into which the simple username will be inserted. This template allows for the creation of a DN by injecting the simple username into the common name (CN) portion of the DN. <strong>This element will need to be customized to reflect your deployment environment.</strong> The template provided in the sample is only an example and is valid only within the LDAP schema distributed with Knox and is represented by the users.ldif file in the {GATEWAY_HOME}/conf directory.</p><p><strong>main.ldapRealm.contextFactory.url
</strong> - this element is the URL that represents the host and port of LDAP server. It also includes the scheme of the protocol to use. This may be either ldap or ldaps depending on whether you are communicating with the LDAP over SSL (higly recommended). <strong>This element will need to be cusomized to reflect your deployment environment.</strong>.</p><p><strong>main.ldapRealm.contextFactory.authenticationMechanism</strong> - this element indicates the type of authentication that should be performed against the LDAP server. The current default value is <code>simple</code> which indicates a simple bind operation. This element should not need to be modified and no mechanism other than a simple bind has been tested for this particular release.</p><p><strong>urls./</strong>** - this element represents a single URL_Ant_Path_Expression and the value the Shiro filter chain to apply to it. This particular sample indicates that all paths into the application have the same Shiro filter ch
ain applied. The paths are relative to the application context path. The use of the value <code>authcBasic</code> here indicates that BASIC authentication is expected for every path into the application. Adding an additional Shiro filter to that chain for validating that the request isSecure() and over SSL can be achieved by changing the value to <code>ssl, authcBasic</code>. It is not likely that you need to change this element for your environment.</p><h4><a id="Active+Directory+-+Special+Note"></a>Active Directory - Special Note</h4><p>You would use LDAP configuration as documented above to authenticate against Active Directory as well.</p><p>Some Active Directory specifc things to keep in mind:</p><p>Typical AD main.ldapRealm.userDnTemplate value looks slightly different, such as cn={0},cn=users,DC=lab,DC=sample,dc=com</p><p>Please compare this with a typical Apache DS main.ldapRealm.userDnTemplate value and make note of the difference. uid={0},ou=people,dc=hadoop,dc=apache,dc
=org</p><p>If your AD is configured to authenticate based on just the cn and password and does not require user DN, you do not have to specify value for main.ldapRealm.userDnTemplate.</p><h4><a id="LDAP+over+SSL+(LDAPS)+Configuration"></a>LDAP over SSL (LDAPS) Configuration</h4><p>In order to communicate with your LDAP server over SSL (again, highly recommended), you will need to modify the topology file in a couple ways and possibly provision some keying material.</p>
+<ol>
+ <li><strong>main.ldapRealm.contextFactory.url</strong> must be changed to have the <code>ldaps</code> protocol scheme and the port must be the SSL listener port on your LDAP server.</li>
+ <li>Identity certificate (keypair) provisioned to LDAP server - your LDAP server specific documentation should indicate what is requried for providing a cert or keypair to represent the LDAP server identity to connecting clients.</li>
+ <li>Trusting the LDAP Server’s public key - if the LDAP Server’s identity certificate is issued by a well known and trusted certificate authority and is already represented in the JRE’s cacerts truststore then you don’t need to do anything for trusting the LDAP server’s cert. If, however, the cert is selfsigned or issued by an untrusted authority you will need to either add it to the cacerts keystore or to another truststore that you may direct Knox to utilize through a system property.</li>
+</ol><h4><a id="Session+Configuration"></a>Session Configuration</h4><p>Knox maps each cluster topology to a web application and leverages standard JavaEE session management.</p><p>To configure session idle timeout for the topology, please specify value of parameter sessionTimeout for ShiroProvider in your topology file. If you do not specify the value for this parameter, it defaults to 30minutes.</p><p>The definition would look like the following in the topoloogy file:</p>
+<pre><code>...
+<provider>
+ <role>authentication</role>
+ <name>ShiroProvider</name>
+ <enabled>true</enabled>
+ <param>
+ <!--
+ Session timeout in minutes. This is really idle timeout.
+ Defaults to 30 minutes, if the property value is not defined.
+ Current client authentication will expire if client idles
+ continuously for more than this value
+ -->
+ <name>sessionTimeout</name>
+ <value>30</value>
+ </param>
+<provider>
+...
+</code></pre><p>At present, ShiroProvider in Knox leverages JavaEE session to maintain authentication state for a user across requests using JSESSIONID cookie. So, a client that authenticated with Knox could pass the JSESSIONID cookie with repeated requests as long as the session has not timed out instead of submitting userid/password with every request. Presenting a valid session cookie in place of userid/password would also perform better as additional credential store lookups are avoided.</p><h3><a id="Advanced+LDAP+Authentication"></a>Advanced LDAP Authentication</h3><p>The default configuration computes the bind DN for incoming user based on userDnTemplate. This does not work in enterprises where users could belong to multiple branches of LDAP tree. You could instead enable advanced configuration that would compute bind DN of incoming user with an LDAP search.</p><h4><a id="Problem+with++userDnTemplate+based+Authentication"></a>Problem with userDnTemplate based Authentication</
h4><p>UserDnTemplate based authentication uses configuration parameter ldapRealm.userDnTemplate. Typical value of userDNTemplate would look like uid={0},ou=people,dc=hadoop,dc=apache,dc=org.</p><p>To compute bind DN of the client, we swap the place holder {0} with login id provided by the client. For example, if the login id provided by the client is "guest’,<br/>the computed bind DN would be uid=guest,ou=people,dc=hadoop,dc=apache,dc=org.</p><p>This keeps configuration simple.</p><p>However, this does not work if users belong to different branches of LDAP DIT. For example, if there are some users under ou=people,dc=hadoop,dc=apache,dc=org and some users under ou=contractors,dc=hadoop,dc=apache,dc=org,<br/>we can not come up with userDnTemplate that would work for all the users.</p><h4><a id="Using+advanced+LDAP+Authentication"></a>Using advanced LDAP Authentication</h4><p>With advanced LDAP authentication, we find the bind DN of the user by searching LDAP directory inste
ad of interpolating bind DN from userDNTemplate. </p><h4><a id="Example+search+filter+to+find+the+client+bind+DN"></a>Example search filter to find the client bind DN</h4><p>Assuming,<br/>ldapRealm.userSearchAttributeName=uid ldapRealm.userObjectClass=person client specified login id = “guest”</p><p>LDAP Filter for doing a search to find the bind DN would be (&(uid=guest)(objectclass=person))</p><p>This could find bind DN to be uid=guest,ou=people,dc=hadoop,dc=apache,dc=org</p><p>Please note that the userSearchAttributeName need not be part of bindDN.</p><p>For example, you could use </p><p>ldapRealm.userSearchAttributeName=email ldapRealm.userObjectClass=person client specified login id = “<a href="mailto:bill.clinton@gmail.com">bill.clinton@gmail.com</a>”</p><p>LDAP Filter for doing a search
to find the bind DN would be (&(email=bill<a href="mailto:.clinton@gmail.com)(objectclass=person)">.clinton@gmail.com)(objectclass=person)</a>)</p><p>This could find bind DN to be uid=billc,ou=contractors,dc=hadoop,dc=apache,dc=org</p><h4><a id="Example+provider+configuration+to+use+advanced+LDAP+authentication"></a>Example provider configuration to use advanced LDAP authentication</h4><p>The example configuration appears verbose due to the presence of liberal comments and illustration of optional parameters and default values. The configuration that you would use could be much shorter if you rely on default values.</p><p><provider></p
>
+<pre><code><role>authentication</role>
+<name>ShiroProvider</name>
+<enabled>true</enabled>
+
+<param>
+ <name>main.ldapRealm</name>
+ <value>org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm</value>
+</param>
+
+<param>
+ <name>main.ldapContextFactory</name>
+ <value>org.apache.hadoop.gateway.shirorealm.KnoxLdapContextFactory
+ </value>
+</param>
+
+<param>
+ <name>main.ldapRealm.contextFactory</name>
+ <value>$ldapContextFactory</value>
+</param>
+
+<!-- update the value based on your ldap directory protocol, host and port -->
+<param>
+ <name>main.ldapRealm.contextFactory.url</name>
+ <value>ldap://hdp.example.com:389</value>
+</param>
+
+<!-- optional, default value: simple
+ Update the value based on mechanisms supported by your ldap directory -->
+<param>
+ <name>main.ldapRealm.contextFactory.authenticationMechanism</name>
+ <value>simple</value>
+</param>
+
+<!-- optional, default value: {0}
+ update the value based on your ldap DIT(directory information tree).
+ ignored if value is defined for main.ldapRealm.userSearchAttributeName -->
+<param>
+ <name>main.ldapRealm.userDnTemplate</name>
+ <value>uid={0},ou=people,dc=hadoop,dc=apache,dc=org</value>
+</param>
+
+<!-- optional, default value: null
+ If you specify a value for this attribute, useDnTemplate
+ specified above would be ignored and user bind DN would be computed using
+ ldap search
+ update the value based on your ldap DIT(directory information layout)
+ value of search attribute should identity the user uniquely -->
+<param>
+ <name>main.ldapRealm.userSearchAttributeName</name>
+ <value>uid</value>
+</param>
+
+<!-- optional, default value: false
+ If the value is true, groups in which user is a member are looked up
+ from LDAP and made available for service level authorization checks -->
+<param>
+ <name>main.ldapRealm.authorizationEnabled</name>
+ <value>true</value>
+</param>
+
[... 2754 lines stripped ...]