You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@knox.apache.org by km...@apache.org on 2013/03/22 20:12:11 UTC
[8/9] git commit: Cleaned up gateway-release directory by adding src
and home directories and moving files there.
Cleaned up gateway-release directory by adding src and home directories and moving files there.
Project: http://git-wip-us.apache.org/repos/asf/incubator-knox/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-knox/commit/800736a8
Tree: http://git-wip-us.apache.org/repos/asf/incubator-knox/tree/800736a8
Diff: http://git-wip-us.apache.org/repos/asf/incubator-knox/diff/800736a8
Branch: refs/heads/master
Commit: 800736a8d7358cb07064bc0c371bab07d5a2f038
Parents: 430f1d8
Author: Kevin Minder <ke...@hortonworks.com>
Authored: Fri Mar 22 14:32:18 2013 -0400
Committer: Kevin Minder <ke...@hortonworks.com>
Committed: Fri Mar 22 14:32:18 2013 -0400
----------------------------------------------------------------------
gateway-release/CHANGES | 11 -
gateway-release/DISCLAIMER | 15 -
gateway-release/INSTALL | 252 -----
gateway-release/ISSUES | 11 -
gateway-release/LICENSE | 805 ---------------
gateway-release/NOTICE | 20 -
gateway-release/README | 87 --
gateway-release/assembly.xml | 85 --
gateway-release/conf/README | 1 -
gateway-release/conf/gateway-site.xml | 39 -
gateway-release/conf/log4j.properties | 29 -
gateway-release/conf/users.ldif | 62 --
gateway-release/deployments/README | 1 -
gateway-release/deployments/sample.xml | 60 --
gateway-release/ext/README | 1 -
gateway-release/home/CHANGES | 11 +
gateway-release/home/DISCLAIMER | 15 +
gateway-release/home/INSTALL | 252 +++++
gateway-release/home/ISSUES | 11 +
gateway-release/home/LICENSE | 805 +++++++++++++++
gateway-release/home/NOTICE | 20 +
gateway-release/home/README | 87 ++
gateway-release/home/conf/README | 1 +
gateway-release/home/conf/gateway-site.xml | 39 +
gateway-release/home/conf/log4j.properties | 29 +
gateway-release/home/conf/users.ldif | 62 ++
gateway-release/home/deployments/README | 1 +
gateway-release/home/deployments/sample.xml | 60 ++
gateway-release/home/ext/README | 1 +
gateway-release/home/lib/README | 1 +
gateway-release/home/samples/ExamplePutFile.groovy | 37 +
.../home/samples/ExampleSubmitJob.groovy | 61 ++
.../home/samples/ExampleSubmitWorkflow.groovy | 92 ++
.../home/samples/SampleComplexCommand.groovy | 69 ++
gateway-release/home/samples/SampleScript.groovy | 29 +
gateway-release/home/samples/SampleService.groovy | 32 +
.../home/samples/SampleSimpleCommand.groovy | 51 +
gateway-release/home/samples/hadoop-examples.jar | Bin 0 -> 142457 bytes
gateway-release/home/templates/topology.xml | 56 +
gateway-release/home/templates/users.ldif | 62 ++
.../home/templates/workflow-configuration.xml | 47 +
.../home/templates/workflow-definition.xml | 36 +
gateway-release/lib/README | 1 -
gateway-release/pom.xml | 2 +-
gateway-release/samples/ExamplePutFile.groovy | 37 -
gateway-release/samples/ExampleSubmitJob.groovy | 61 --
.../samples/ExampleSubmitWorkflow.groovy | 92 --
.../samples/SampleComplexCommand.groovy | 69 --
gateway-release/samples/SampleScript.groovy | 29 -
gateway-release/samples/SampleService.groovy | 32 -
gateway-release/samples/SampleSimpleCommand.groovy | 51 -
gateway-release/samples/hadoop-examples.jar | Bin 142457 -> 0 bytes
gateway-release/src/assembly.xml | 81 ++
gateway-release/templates/topology.xml | 56 -
gateway-release/templates/users.ldif | 62 --
.../templates/workflow-configuration.xml | 47 -
gateway-release/templates/workflow-definition.xml | 36 -
57 files changed, 2049 insertions(+), 2053 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/CHANGES
----------------------------------------------------------------------
diff --git a/gateway-release/CHANGES b/gateway-release/CHANGES
deleted file mode 100644
index 40a6ddc..0000000
--- a/gateway-release/CHANGES
+++ /dev/null
@@ -1,11 +0,0 @@
-------------------------------------------------------------------------------
-Changes v0.1.0 - v0.2.0
-------------------------------------------------------------------------------
-HTTPS Support (Client side)
-Oozie Support
-Protected DataNode URL query strings
-Pluggable Identity Asserters
-Principal Mapping
-URL Rewriting Enhancements
-KnoxShell Client DSL
-
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/DISCLAIMER
----------------------------------------------------------------------
diff --git a/gateway-release/DISCLAIMER b/gateway-release/DISCLAIMER
deleted file mode 100644
index e6af5c0..0000000
--- a/gateway-release/DISCLAIMER
+++ /dev/null
@@ -1,15 +0,0 @@
-Apache Knox is an effort undergoing incubation at the Apache Software
-Foundation (ASF), sponsored by the Apache Incubator PMC.
-
-Incubation is required of all newly accepted projects until a further review
-indicates that the infrastructure, communications, and decision making process
-have stabilized in a manner consistent with other successful ASF projects.
-
-While incubation status is not necessarily a reflection of the completeness
-or stability of the code, it does indicate that the project has yet to be
-fully endorsed by the ASF.
-
-For more information about the incubation status of the Apache Knox project you
-can go to the following page:
-
-http://incubator.apache.org/projects/knox.html
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/INSTALL
----------------------------------------------------------------------
diff --git a/gateway-release/INSTALL b/gateway-release/INSTALL
deleted file mode 100644
index f320165..0000000
--- a/gateway-release/INSTALL
+++ /dev/null
@@ -1,252 +0,0 @@
-------------------------------------------------------------------------------
-Requirements
-------------------------------------------------------------------------------
-Java:
- Java 1.6 or later
-
-Hadoop Cluster:
- A local installation of a Hadoop Cluster is required at this time. Hadoop
- EC2 cluster and/or Sandbox installations are currently difficult to access
- remotely via the Gateway. The EC2 and Sandbox limitation is caused by
- Hadoop services running with internal IP addresses. For the Gateway to work
- in these cases it will need to be deployed on the EC2 cluster or Sandbox, at
- this time.
-
- The instructions that follow assume that the Gateway is *not* collocated
- with the Hadoop clusters themselves and (most importantly) that the
- hostnames and IP addresses of the cluster services are accessible by the
- gateway where ever it happens to be running.
-
- The Hadoop cluster should be ensured to have WebHDFS, WebHCat
- (i.e. Templeton) and Oozie configured, deployed and running.
-
-------------------------------------------------------------------------------
-Installation and Deployment Instructions
-------------------------------------------------------------------------------
-1. Install
- Download and extract the gateway-0.2.0-SNAPSHOT.zip file into the
- installation directory that will contain your GATEWAY_HOME
- jar xf gateway-0.2.0-SNAPSHOT.zip
- This will create a directory 'gateway' in your current directory.
-
-2. Enter Gateway Home directory
- cd gateway
- The fully qualified name of this directory will be referenced as
- {GATEWAY_HOME} throughout the remainder of this document.
-
-3. Start the demo LDAP server (ApacheDS)
- a. First, understand that the LDAP server provided here is for demonstration
- purposes. You may configure the LDAP specifics within the topology
- descriptor for the cluster as described in step 5 below, in order to
- customize what LDAP instance to use. The assumption is that most users
- will leverage the demo LDAP server while evaluating this release and
- should therefore continue with the instructions here in step 3.
- b. Edit {GATEWAY_HOME}/conf/users.ldif if required and add your users and
- groups to the file. A number of normal Hadoop users
- (e.g. hdfs, mapred, hcat, hive) have already been included. Note that
- the passwords in this file are "fictitious" and have nothing to do with
- the actual accounts on the Hadoop cluster you are using. There is also
- a copy of this file in the templates directory that you can use to start
- over if necessary.
- c. Start the LDAP server - pointing it to the config dir where it will find
- the users.ldif file in the conf directory.
- java -jar bin/ldap-0.2.0-SNAPSHOT.jar conf &
- There are a number of log messages of the form "Created null." that can
- safely be ignored. Take note of the port on which it was started as this
- needs to match later configuration. This will create a directory named
- 'org.apache.hadoop.gateway.security.EmbeddedApacheDirectoryServer' that
- can safely be ignored.
-
-4. Start the Gateway server
- java -jar bin/gateway-server-0.2.0-SNAPSHOT.jar
- a. Take note of the port identified in the logging output as you will need this for
- accessing the gateway.
- b. The server will prompt you for the master secret (password). This secret is used
- to secure artifacts used to secure artifacts used by the gateway server for
- things like SSL, credential/password aliasing. This secret will have to be entered
- at startup unless you choose to persist it. Remember this secret and keep it safe.
- It represents the keys to the kingdom. See the Persisting the Master section for
- more information.
-
-5. Configure the Gateway with the topology of your Hadoop cluster
- a. Edit the file {GATEWAY_HOME}/deployments/sample.xml
- b. Change the host and port in the urls of the <service> elements for
- NAMENODE, TEMPLETON and OOZIE services to match your Hadoop cluster
- deployment.
- c. The default configuration contains the LDAP URL for a LDAP server. By
- default that file is configured to access the demo ApacheDS based LDAP
- server and its default configuration. By default, this server listens on
- port 33389. Optionally, you can change the LDAP URL for the LDAP server
- to be used for authentication. This is set via the
- main.ldapRealm.contextFactory.url property in the
- <gateway><provider><authentication> section.
- d. Save the file. The directory {GATEWAY_HOME}/deployments is monitored
- by the Gateway server and reacts to the discovery of a new or changed
- cluster topology descriptor by provisioning the endpoints and required
- filter chains to serve the needs of each cluster as described by the
- topology file. Note that the name of the file excluding the extension
- is also used as the path for that cluster in the URL. So for example
- the sample.xml file will result in Gateway URLs of the form
- http://{gateway-host}:{gateway-port}/gateway/sample/namenode/api/v1
-
-6. Test the installation and configuration of your Gateway
- Invoke the LISTSATUS operation on HDFS represented by your configured
- NAMENODE by using your web browser or curl:
-
- curl -i -k -u hdfs:hdfs-password -X GET \
- 'https://localhost:8443/gateway/sample/namenode/api/v1/?op=LISTSTATUS'
-
- 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.
-
- 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"}
- ]}}
-
- For additional information on WebHDFS, Templeton/WebHCat and Oozie
- REST APIs, see the following URLs respectively:
-
- http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/WebHDFS.html
- http://people.apache.org/~thejas/templeton_doc_v1/
- http://oozie.apache.org/docs/3.3.1/WebServicesAPI.html
-
-------------------------------------------------------------------------------
-Persisting the Master
-------------------------------------------------------------------------------
-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.
-
-You may persist the master secret by supplying the *-persist-master* 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
-order to protect the persisted password.
-
-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.
-
-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.
-
-A specific user should be created to run the gateway this will protect a persisted master file.
-
-------------------------------------------------------------------------------
-Management of Security Artifacts
-------------------------------------------------------------------------------
-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. These artifacts can be managed from outside of
-the gateway instances or generated and populated by the gateway instance itself.
-
-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.
-
-Upon start of the gateway server we:
-
-1. Look for an identity store at conf/security/keystores/gateway.jks. The identity store contains the certificate
- and private key used to represent the identity of the server for SSL connections and signtature creation.
- a. 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.
- b. 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 with called gateway-identity.
-2. Look for a credential store at conf/security/keystores/__gateway-credentials.jceks. 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.
- a. If there is no credential store found then we create one and populate it with a generated passphrase for the alias
- gateway-identity-passphrase. This is coordinated with the population of the self-signed cert into the identity-store.
- b. 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.
-
-Upon deployment of a Hadoop cluster topology within the gateway we:
-
-1. 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 conf/security/keystores/sample-credentials.jceks. This topology specific credential store is used for storing
- secrets/passwords that are used for encrypting sensitive data with topology specific keys.
- a. 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 programmatically set the value of the secret or choose to have the value for the specified alias
- generated through the AliasService..
- b. If a credential store is found then we ensure that it can be loaded with the provided master secret and the confgured
- providers have the opportunity to ensure that the aliases are populated and if not to populate them.
-
- By leveraging the algorithm described above we can provide a window of opportunity for management of these artifacts in a
- number of ways.
-
- 1. 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.
- 2. 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.
-
-Summary of Secrets to be Managed:
-
-1. Master secret - the same for all gateway instances in a cluster of gateways
-2. All security related artifacts are protected with the master secret
-3. 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
-4. 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 failover 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.
-
-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 hostname verification problems will ensue. Obviously, truststores will
-need to be taken into account as well.
-
-
-------------------------------------------------------------------------------
-Mapping Gateway URLs to Hadoop cluster URLs
-------------------------------------------------------------------------------
-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. Examples of mappings for the NameNode and
-Templeton are shown below. These mapping are generated from the combination
-of the Gateway configuration file (i.e. {GATEWAY_HOME}/gateway-site.xml)
-and the cluster topology descriptors
-(e.g. {GATEWAY_HOME}/deployments/<cluster-name>.xml).
-
- HDFS (NameNode)
- Gateway: http://<gateway-host>:<gateway-port>/<gateway-path>/<cluster-name>/namenode/api/v1
- Cluster: http://<namenode-host>:50070/webhdfs/v1
- WebHCat (Templeton)
- Gateway: http://<gateway-host>:<gateway-port>/<gateway-path>/<cluster-name>/templeton/api/v1
- Cluster: http://<templeton-host>:50111/templeton/v1
- Oozie
- Gateway: http://<gateway-host>:<gateway-port>/<gateway-path>/<cluster-name>/oozie/api/v1
- Cluster: http://<templeton-host>:11000/oozie/v1
-
-The values for <gateway-host>, <gateway-port>, <gateway-path> are provided via
-the Gateway configuration file (i.e. {GATEWAY_HOME}/gateway-site.xml).
-
-The value for <cluster-name> is derived from the name of the cluster topology
-descriptor (e.g. {GATEWAY_HOME}/deployments/<cluster-name>.xml).
-
-The value for <namenode-host> and <templeton-host> is provided via the cluster
-topology descriptor (e.g. {GATEWAY_HOME}/deployments/<cluster-name>.xml).
-
-Note: The ports 50070, 50111 and 11000 are the defaults for NameNode,
- Templeton and Oozie respectively. Their values can also be provided via
- the cluster topology descriptor if your Hadoop cluster uses different
- ports.
-
-------------------------------------------------------------------------------
-Usage Examples
-------------------------------------------------------------------------------
-Please see the Apache Knox Gateway website for detailed examples.
-http://knox.incubator.apache.org/examples.html
-
-------------------------------------------------------------------------------
-Enabling logging
-------------------------------------------------------------------------------
-If necessary you can enable additional logging by editing the log4j.properties
-file in the conf directory. Changing the rootLogger value from ERROR to DEBUG
-will generate a large amount of debug logging. A number of useful, more fine
-loggers are also provided in the file.
-
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/ISSUES
----------------------------------------------------------------------
diff --git a/gateway-release/ISSUES b/gateway-release/ISSUES
deleted file mode 100644
index 290956e..0000000
--- a/gateway-release/ISSUES
+++ /dev/null
@@ -1,11 +0,0 @@
-------------------------------------------------------------------------------
-Know Issues
-------------------------------------------------------------------------------
-The Gateway cannot be be used against either EC2 clusters or Hadoop Sandbox
-VMs unless the gateway is deployed within the EC2 cluster or the on the
-Sandbox VM.
-
-If the cluster deployment descriptors in {GATEWAY_HOME}/deployments are
-incorrect, the errors logged by the gateway are overly detailed and not
-diagnostic enough.
-
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/LICENSE
----------------------------------------------------------------------
diff --git a/gateway-release/LICENSE b/gateway-release/LICENSE
deleted file mode 100644
index d782ea3..0000000
--- a/gateway-release/LICENSE
+++ /dev/null
@@ -1,805 +0,0 @@
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- 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.
-
-
-Apache Knox Subcomponents:
-
-Apache Knox includes a number of subcomponents with separate copyright notices
-and license terms. Your use of these subcomponents is subject to the terms and
-conditions of the following licenses.
-
-
-For TODO.jar (Jerico)
-
-Eclipse Public License - v 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC
-LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
-CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-
-"Contribution" means:
-
-a) in the case of the initial Contributor, the initial code and documentation
-distributed under this Agreement, and
-
-b) in the case of each subsequent Contributor:
-
-i) changes to the Program, and
-
-ii) additions to the Program;
-
-where such changes and/or additions to the Program originate from and are
-distributed by that particular Contributor. A Contribution 'originates' from a
-Contributor if it was added to the Program by such Contributor itself or anyone
-acting on such Contributor's behalf. Contributions do not include additions to
-the Program which: (i) are separate modules of software distributed in
-conjunction with the Program under their own license agreement, and (ii) are not
-derivative works of the Program.
-
-"Contributor" means any person or entity that distributes the Program.
-
-"Licensed Patents" mean patent claims licensable by a Contributor which are
-necessarily infringed by the use or sale of its Contribution alone or when
-combined with the Program.
-
-"Program" means the Contributions distributed in accordance with this Agreement.
-
-"Recipient" means anyone who receives the Program under this Agreement,
-including all Contributors.
-
-2. GRANT OF RIGHTS
-
-a) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free copyright license to
-reproduce, prepare derivative works of, publicly display, publicly perform,
-distribute and sublicense the Contribution of such Contributor, if any, and such
-derivative works, in source code and object code form.
-
-b) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
-Patents to make, use, sell, offer to sell, import and otherwise transfer the
-Contribution of such Contributor, if any, in source code and object code form.
-This patent license shall apply to the combination of the Contribution and the
-Program if, at the time the Contribution is added by the Contributor, such
-addition of the Contribution causes such combination to be covered by the
-Licensed Patents. The patent license shall not apply to any other combinations
-which include the Contribution. No hardware per se is licensed hereunder.
-
-c) Recipient understands that although each Contributor grants the licenses to
-its Contributions set forth herein, no assurances are provided by any
-Contributor that the Program does not infringe the patent or other intellectual
-property rights of any other entity. Each Contributor disclaims any liability to
-Recipient for claims brought by any other entity based on infringement of
-intellectual property rights or otherwise. As a condition to exercising the
-rights and licenses granted hereunder, each Recipient hereby assumes sole
-responsibility to secure any other intellectual property rights needed, if any.
-For example, if a third party patent license is required to allow Recipient to
-distribute the Program, it is Recipient's responsibility to acquire that license
-before distributing the Program.
-
-d) Each Contributor represents that to its knowledge it has sufficient copyright
-rights in its Contribution, if any, to grant the copyright license set forth in
-this Agreement.
-
-3. REQUIREMENTS
-
-A Contributor may choose to distribute the Program in object code form under its
-own license agreement, provided that:
-
-a) it complies with the terms and conditions of this Agreement; and
-
-b) its license agreement:
-
-i) effectively disclaims on behalf of all Contributors all warranties and
-conditions, express and implied, including warranties or conditions of title and
-non-infringement, and implied warranties or conditions of merchantability and
-fitness for a particular purpose;
-
-ii) effectively excludes on behalf of all Contributors all liability for
-damages, including direct, indirect, special, incidental and consequential
-damages, such as lost profits;
-
-iii) states that any provisions which differ from this Agreement are offered by
-that Contributor alone and not by any other party; and
-
-iv) states that source code for the Program is available from such Contributor,
-and informs licensees how to obtain it in a reasonable manner on or through a
-medium customarily used for software exchange.
-
-When the Program is made available in source code form:
-
-a) it must be made available under this Agreement; and
-
-b) a copy of this Agreement must be included with each copy of the Program.
-
-Contributors may not remove or alter any copyright notices contained within the
-Program.
-
-Each Contributor must identify itself as the originator of its Contribution, if
-any, in a manner that reasonably allows subsequent Recipients to identify the
-originator of the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-
-Commercial distributors of software may accept certain responsibilities with
-respect to end users, business partners and the like. While this license is
-intended to facilitate the commercial use of the Program, the Contributor who
-includes the Program in a commercial product offering should do so in a manner
-which does not create potential liability for other Contributors. Therefore, if
-a Contributor includes the Program in a commercial product offering, such
-Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
-every other Contributor ("Indemnified Contributor") against any losses, damages
-and costs (collectively "Losses") arising from claims, lawsuits and other legal
-actions brought by a third party against the Indemnified Contributor to the
-extent caused by the acts or omissions of such Commercial Contributor in
-connection with its distribution of the Program in a commercial product
-offering. The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement. In order
-to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
-Contributor in writing of such claim, and b) allow the Commercial Contributor
-to control, and cooperate with the Commercial Contributor in, the defense and
-any related settlement negotiations. The Indemnified Contributor may
-participate in any such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial product
-offering, Product X. That Contributor is then a Commercial Contributor. If that
-Commercial Contributor then makes performance claims, or offers warranties
-related to Product X, those performance claims and warranties are such
-Commercial Contributor's responsibility alone. Under this section, the
-Commercial Contributor would have to defend claims against the other
-Contributors related to those performance claims and warranties, and if a court
-requires any other Contributor to pay any damages as a result, the Commercial
-Contributor must pay those damages.
-
-5. NO WARRANTY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
-IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
-NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
-Recipient is solely responsible for determining the appropriateness of using and
-distributing the Program and assumes all risks associated with its exercise of
-rights under this Agreement , including but not limited to the risks and costs
-of program errors, compliance with applicable laws, damage to or loss of data,
-programs or equipment, and unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
-CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
-PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
-STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
-GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-
-If any provision of this Agreement is invalid or unenforceable under applicable
-law, it shall not affect the validity or enforceability of the remainder of the
-terms of this Agreement, and without further action by the parties hereto, such
-provision shall be reformed to the minimum extent necessary to make such
-provision valid and enforceable.
-
-If Recipient institutes patent litigation against any entity (including a
-cross-claim or counterclaim in a lawsuit) alleging that the Program itself
-(excluding combinations of the Program with other software or hardware)
-infringes such Recipient's patent(s), then such Recipient's rights granted under
-Section 2(b) shall terminate as of the date such litigation is filed.
-
-All Recipient's rights under this Agreement shall terminate if it fails to
-comply with any of the material terms or conditions of this Agreement and does
-not cure such failure in a reasonable period of time after becoming aware of
-such noncompliance. If all Recipient's rights under this Agreement terminate,
-Recipient agrees to cease use and distribution of the Program as soon as
-reasonably practicable. However, Recipient's obligations under this Agreement
-and any licenses granted by Recipient relating to the Program shall continue and
-survive.
-
-Everyone is permitted to copy and distribute copies of this Agreement, but in
-order to avoid inconsistency the Agreement is copyrighted and may only be
-modified in the following manner. The Agreement Steward reserves the right to
-publish new versions (including revisions) of this Agreement from time to time.
-No one other than the Agreement Steward has the right to modify this Agreement.
-The Eclipse Foundation is the initial Agreement Steward. The Eclipse Foundation
-may assign the responsibility to serve as the Agreement Steward to a suitable
-separate entity. Each new version of the Agreement will be given a
-distinguishing version number. The Program (including Contributions) may always
-be distributed subject to the version of the Agreement under which it was
-received. In addition, after a new version of the Agreement is published,
-Contributor may elect to distribute the Program (including its Contributions)
-under the new version. Except as expressly stated in Sections 2(a) and 2(b)
-above, Recipient receives no rights or licenses to the intellectual property of
-any Contributor under this Agreement, whether expressly, by implication,
-estoppel or otherwise. All rights in the Program not expressly granted under
-this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and the
-intellectual property laws of the United States of America. No party to this
-Agreement will bring a legal action under this Agreement more than one year
-after the cause of action arose. Each party waives its rights to a jury trial in
-any resulting litigation.
-
-
-For TODO.jar (Jave EE Servlet API)
-
-COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0
-
-1. Definitions.
-
- 1.1. Contributor. means each individual or entity that creates or contributes
- to the creation of Modifications.
-
- 1.2. Contributor Version. means the combination of the Original Software,
- prior Modifications used by a Contributor (if any), and the
- Modifications made by that particular Contributor.
-
- 1.3. Covered Software. means (a) the Original Software, or (b) Modifications,
- or (c) the combination of files containing Original Software with files
- containing Modifications, in each case including portions thereof.
-
- 1.4. Executable. means the Covered Software in any form other than Source
- Code.
-
- 1.5. Initial Developer. means the individual or entity that first makes
- Original Software available under this License.
-
- 1.6. Larger Work. means a work which combines Covered Software or portions
- thereof with code not governed by the terms of this License.
-
- 1.7. License. means this document.
-
- 1.8. Licensable. means having the right to grant, to the maximum extent
- possible, whether at the time of the initial grant or subsequently
- acquired, any and all of the rights conveyed herein.
-
- 1.9. Modifications. means the Source Code and Executable form of any of the
- following:
-
- A. Any file that results from an addition to, deletion from or
- modification of the contents of a file containing Original Software
- or previous Modifications;
-
- B. Any new file that contains any part of the Original Software or
- previous Modification; or
-
- C. Any new file that is contributed or otherwise made available under
- the terms of this License.
-
- 1.10. Original Software. means the Source Code and Executable form of
- computer software code that is originally released under this License.
-
- 1.11. Patent Claims. means any patent claim(s), now owned or hereafter
- acquired, including without limitation, method, process, and apparatus
- claims, in any patent Licensable by grantor.
-
- 1.12. Source Code. means (a) the common form of computer software code in
- which modifications are made and (b) associated documentation included
- in or with such code.
-
- 1.13. You. (or .Your.) means an individual or a legal entity exercising
- rights under, and complying with all of the terms of, this License. For
- legal entities, .You. includes any entity which controls, is controlled
- by, or is under common control with You. For purposes of this
- definition, .control. means (a) the power, direct or indirect, to cause
- the direction or management of such entity, whether by contract or
- otherwise, or (b) ownership of more than fifty percent (50%) of the
- outstanding shares or beneficial ownership of such entity.
-
-2. License Grants.
-
- 2.1. The Initial Developer Grant.
-
- Conditioned upon Your compliance with Section 3.1 below and subject to
- third party intellectual property claims, the Initial Developer hereby
- grants You a world-wide, royalty-free, non-exclusive license:
-
- (a) under intellectual property rights (other than patent or trademark)
- Licensable by Initial Developer, to use, reproduce, modify, display,
- perform, sublicense and distribute the Original Software (or
- portions thereof), with or without Modifications, and/or as part of
- a Larger Work; and
-
- (b) under Patent Claims infringed by the making, using or selling of
- Original Software, to make, have made, use, practice, sell, and
- offer for sale, and/or otherwise dispose of the Original Software
- (or portions thereof).
-
- (c) The licenses granted in Sections 2.1(a) and (b) are effective on the
- date Initial Developer first distributes or otherwise makes the
- Original Software available to a third party under the terms of this
- License.
-
- (d) Notwithstanding Section 2.1(b) above, no patent license is granted:
- (1) for code that You delete from the Original Software, or (2) for
- infringements caused by: (i) the modification of the Original
- Software, or (ii) the combination of the Original Software with
- other software or devices.
-
- 2.2. Contributor Grant.
-
- Conditioned upon Your compliance with Section 3.1 below and subject to third
- party intellectual property claims, each Contributor hereby grants You a
- world-wide, royalty-free, non-exclusive license:
-
- (a) under intellectual property rights (other than patent or trademark)
- Licensable by Contributor to use, reproduce, modify, display,
- perform, sublicense and distribute the Modifications created by such
- Contributor (or portions thereof), either on an unmodified basis,
- with other Modifications, as Covered Software and/or as part of a
- Larger Work; and
-
- (b) under Patent Claims infringed by the making, using, or selling of
- Modifications made by that Contributor either alone and/or in
- combination with its Contributor Version (or portions of such
- combination), to make, use, sell, offer for sale, have made, and/or
- otherwise dispose of: (1) Modifications made by that Contributor (or
- portions thereof); and (2) the combination of Modifications made by
- that Contributor with its Contributor Version (or portions of such
- combination).
-
- (c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on
- the date Contributor first distributes or otherwise makes the
- Modifications available to a third party.
-
- (d) Notwithstanding Section 2.2(b) above, no patent license is granted:
- (1) for any code that Contributor has deleted from the Contributor
- Version; (2) for infringements caused by: (i) third party
- modifications of Contributor Version, or (ii) the combination of
- Modifications made by that Contributor with other software (except
- as part of the Contributor Version) or other devices; or (3) under
- Patent Claims infringed by Covered Software in the absence of
- Modifications made by that Contributor.
-
-3. Distribution Obligations.
-
- 3.1. Availability of Source Code.
- Any Covered Software that You distribute or otherwise make available in
- Executable form must also be made available in Source Code form and that
- Source Code form must be distributed only under the terms of this License.
- You must include a copy of this License with every copy of the Source Code
- form of the Covered Software You distribute or otherwise make available.
- You must inform recipients of any such Covered Software in Executable form
- as to how they can obtain such Covered Software in Source Code form in a
- reasonable manner on or through a medium customarily used for software
- exchange.
-
- 3.2. Modifications.
- The Modifications that You create or to which You contribute are governed
- by the terms of this License. You represent that You believe Your
- Modifications are Your original creation(s) and/or You have sufficient
- rights to grant the rights conveyed by this License.
-
- 3.3. Required Notices.
- You must include a notice in each of Your Modifications that identifies
- You as the Contributor of the Modification. You may not remove or alter
- any copyright, patent or trademark notices contained within the Covered
- Software, or any notices of licensing or any descriptive text giving
- attribution to any Contributor or the Initial Developer.
-
- 3.4. Application of Additional Terms.
- You may not offer or impose any terms on any Covered Software in Source
- Code form that alters or restricts the applicable version of this License
- or the recipients. rights hereunder. You may choose to offer, and to
- charge a fee for, warranty, support, indemnity or liability obligations to
- one or more recipients of Covered Software. However, you may do so only on
- Your own behalf, and not on behalf of the Initial Developer or any
- Contributor. You must make it absolutely clear that any such warranty,
- support, indemnity or liability obligation is offered by You alone, and
- You hereby agree to indemnify the Initial Developer and every Contributor
- for any liability incurred by the Initial Developer or such Contributor as
- a result of warranty, support, indemnity or liability terms You offer.
-
- 3.5. Distribution of Executable Versions.
- You may distribute the Executable form of the Covered Software under the
- terms of this License or under the terms of a license of Your choice,
- which may contain terms different from this License, provided that You are
- in compliance with the terms of this License and that the license for the
- Executable form does not attempt to limit or alter the recipient.s rights
- in the Source Code form from the rights set forth in this License. If You
- distribute the Covered Software in Executable form under a different
- license, You must make it absolutely clear that any terms which differ
- from this License are offered by You alone, not by the Initial Developer
- or Contributor. You hereby agree to indemnify the Initial Developer and
- every Contributor for any liability incurred by the Initial Developer or
- such Contributor as a result of any such terms You offer.
-
- 3.6. Larger Works.
- You may create a Larger Work by combining Covered Software with other code
- not governed by the terms of this License and distribute the Larger Work
- as a single product. In such a case, You must make sure the requirements
- of this License are fulfilled for the Covered Software.
-
-4. Versions of the License.
-
- 4.1. New Versions.
- Sun Microsystems, Inc. is the initial license steward and may publish
- revised and/or new versions of this License from time to time. Each
- version will be given a distinguishing version number. Except as provided
- in Section 4.3, no one other than the license steward has the right to
- modify this License.
-
- 4.2. Effect of New Versions.
- You may always continue to use, distribute or otherwise make the Covered
- Software available under the terms of the version of the License under
- which You originally received the Covered Software. If the Initial
- Developer includes a notice in the Original Software prohibiting it from
- being distributed or otherwise made available under any subsequent version
- of the License, You must distribute and make the Covered Software
- available under the terms of the version of the License under which You
- originally received the Covered Software. Otherwise, You may also choose
- to use, distribute or otherwise make the Covered Software available under
- the terms of any subsequent version of the License published by the
- license steward.
-
- 4.3. Modified Versions.
- When You are an Initial Developer and You want to create a new license for
- Your Original Software, You may create and use a modified version of this
- License if You: (a) rename the license and remove any references to the
- name of the license steward (except to note that the license differs from
- this License); and (b) otherwise make it clear that the license contains
- terms which differ from this License.
-
-5. DISCLAIMER OF WARRANTY.
-
- COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN .AS IS. BASIS, WITHOUT
- WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
- LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS,
- MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK
- AS TO THE QUALITY AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD
- ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL
- DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
- SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN
- ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED
- HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
-
-6. TERMINATION.
-
- 6.1. This License and the rights granted hereunder will terminate
- automatically if You fail to comply with terms herein and fail to
- cure such breach within 30 days of becoming aware of the breach.
- Provisions which, by their nature, must remain in effect beyond the
- termination of this License shall survive.
-
- 6.2. If You assert a patent infringement claim (excluding declaratory
- judgment actions) against Initial Developer or a Contributor (the
- Initial Developer or Contributor against whom You assert such claim
- is referred to as .Participant.) alleging that the Participant
- Software (meaning the Contributor Version where the Participant is a
- Contributor or the Original Software where the Participant is the
- Initial Developer) directly or indirectly infringes any patent, then
- any and all rights granted directly or indirectly to You by such
- Participant, the Initial Developer (if the Initial Developer is not
- the Participant) and all Contributors under Sections 2.1 and/or 2.2
- of this License shall, upon 60 days notice from Participant terminate
- prospectively and automatically at the expiration of such 60 day
- notice period, unless if within such 60 day period You withdraw Your
- claim with respect to the Participant Software against such
- Participant either unilaterally or pursuant to a written agreement
- with Participant.
-
- 6.3. In the event of termination under Sections 6.1 or 6.2 above, all end
- user licenses that have been validly granted by You or any
- distributor hereunder prior to termination (excluding licenses
- granted to You by any distributor) shall survive termination.
-
-7. LIMITATION OF LIABILITY.
-
- UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING
- NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY
- OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF
- ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL,
- INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT
- LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK STOPPAGE,
- COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
- LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF
- SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR
- DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY.S NEGLIGENCE TO THE EXTENT
- APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
- EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS
- EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
-
-8. U.S. GOVERNMENT END USERS.
-
- The Covered Software is a .commercial item,. as that term is defined in 48
- C.F.R. 2.101 (Oct. 1995), consisting of .commercial computer software. (as
- that term is defined at 48 C.F.R. ? 252.227-7014(a)(1)) and commercial
- computer software documentation. as such terms are used in 48 C.F.R. 12.212
- (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1
- through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered
- Software with only those rights set forth herein. This U.S. Government Rights
- clause is in lieu of, and supersedes, any other FAR, DFAR, or other clause or
- provision that addresses Government rights in computer software under this
- License.
-
-9. MISCELLANEOUS.
-
- This License represents the complete agreement concerning subject matter
- hereof. If any provision of this License is held to be unenforceable, such
- provision shall be reformed only to the extent necessary to make it
- enforceable. This License shall be governed by the law of the jurisdiction
- specified in a notice contained within the Original Software (except to the
- extent applicable law, if any, provides otherwise), excluding such
- jurisdiction's conflict-of-law provisions. Any litigation relating to this
- License shall be subject to the jurisdiction of the courts located in the
- jurisdiction and venue specified in a notice contained within the Original
- Software, with the losing party responsible for costs, including, without
- limitation, court costs and reasonable attorneys. fees and expenses. The
- application of the United Nations Convention on Contracts for the
- International Sale of Goods is expressly excluded. Any law or regulation
- which provides that the language of a contract shall be construed against
- the drafter shall not apply to this License. You agree that You alone are
- responsible for compliance with the United States export administration
- regulations (and the export control laws and regulation of any other
- countries) when You use, distribute or otherwise make available any Covered
- Software.
-
-10. RESPONSIBILITY FOR CLAIMS.
-
- As between Initial Developer and the Contributors, each party is responsible
- for claims and damages arising, directly or indirectly, out of its
- utilization of rights under this License and You agree to work with Initial
- Developer and Contributors to distribute such responsibility on an equitable
- basis. Nothing herein is intended or shall be deemed to constitute any
- admission of liability.
-
- NOTICE PURSUANT TO SECTION 9 OF THE COMMON DEVELOPMENT AND DISTRIBUTION
- LICENSE (CDDL)
-
- The code released under the CDDL shall be governed by the laws of the State
- of California (excluding conflict-of-law provisions). Any litigation relating
- to this License shall be subject to the jurisdiction of the Federal Courts of
- the Northern District of California and the state courts of the State of
- California, with venue lying in Santa Clara County, California.
-
-
-zlib/libpng license
-
-This software is provided 'as-is', without any express or implied warranty. In
-no event will the authors be held liable for any damages arising from the use of
-this software.
-
-Permission is granted to anyone to use this software for any purpose, including
-commercial applications, and to alter it and redistribute it freely, subject to
-the following restrictions:
-
- 1. The origin of this software must not be misrepresented; you must not claim
- that you wrote the original software. If you use this software in a
- product, an acknowledgment in the product documentation would be
- appreciated but is not required.
- 2. Altered source versions must be plainly marked as such, and must not be
- misrepresented as being the original software.
- 3. This notice may not be removed or altered from any source distribution.
-
-
-bzip2 license
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- 1. Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
- 2. The origin of this software must not be misrepresented; you must not claim
- that you wrote the original software. If you use this software in a
- product, an acknowledgment in the product documentation would be
- appreciated but is not required.
- 3. Altered source versions must be plainly marked as such, and must not be
- misrepresented as being the original software.
- 4. The name of the author may not be used to endorse or promote products
- derived from this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
-SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
-IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
-OF SUCH DAMAGE.
-
-Julian Seward, Cambridge, UK.
-jseward@acm.org
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/NOTICE
----------------------------------------------------------------------
diff --git a/gateway-release/NOTICE b/gateway-release/NOTICE
deleted file mode 100644
index 4ff0653..0000000
--- a/gateway-release/NOTICE
+++ /dev/null
@@ -1,20 +0,0 @@
-=========================================================================
-== NOTICE file corresponding to the section 4 d of ==
-== the Apache License, Version 2.0, ==
-== in this case for the Apache Knox distribution. ==
-=========================================================================
-
-Apache Knox
-Copyright 2012-2013 The Apache Software Foundation
-
-This product includes software developed by
-The Apache Software Foundation (http://www.apache.org/).
-
-This product includes software (Jerico) developed by
-SourceForge (http://sourceforge.net/projects/jerichohtml/ and see http://jericho.htmlparser.net/)
-
-This product includes software (Simple Logging Facade for Java, SL4J) developed by
-GitHub (https://github.com/qos-ch/slf4j/ and see http://www.slf4j.org/)
-
-This product includes software (Java EE Servlet API) developed by
-? (?).
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/README
----------------------------------------------------------------------
diff --git a/gateway-release/README b/gateway-release/README
deleted file mode 100644
index 3d496d6..0000000
--- a/gateway-release/README
+++ /dev/null
@@ -1,87 +0,0 @@
-------------------------------------------------------------------------------
-README file for Hadoop Gateway
-------------------------------------------------------------------------------
-This distribution includes cryptographic software. The country in
-which you currently reside may have restrictions on the import,
-possession, use, and/or re-export to another country, of
-encryption software. BEFORE using any encryption software, please
-check your country's laws, regulations and policies concerning the
-import, possession, or use, and re-export of encryption software, to
-see if this is permitted. See <http://www.wassenaar.org/> for more
-information.
-
-The U.S. Government Department of Commerce, Bureau of Industry and
-Security (BIS), has classified this software as Export Commodity
-Control Number (ECCN) 5D002.C.1, which includes information security
-software using or performing cryptographic functions with asymmetric
-algorithms. The form and manner of this Apache Software Foundation
-distribution makes it eligible for export under the License Exception
-ENC Technology Software Unrestricted (TSU) exception (see the BIS
-Export Administration Regulations, Section 740.13) for both object
-code and source code.
-
-The following provides more details on the included cryptographic
-software:
- This package includes the use of ApacheDS which is dependent upon the
-Bouncy Castle Crypto APIs written by the Legion of the Bouncy Castle
-http://www.bouncycastle.org/ feedback-crypto@bouncycastle.org.
-
-------------------------------------------------------------------------------
-Description
-------------------------------------------------------------------------------
-The charter for the Gateway project is to simplify and normalize the
-deployment and implementation of secure Hadoop clusters as well as be
-a centralize access point for the service specific REST APIs exposed from
-within the cluster.
-
-Milestone-1 of this project intends to demonstrate the ability to dynamically
-provision reverse proxy capabilities with filter chains that meet the cluster
-specific needs for authentication.
-
-HTTP BASIC authentication with identity being asserted to the rest of the
-cluster via Pseudo/Simple authentication will be demonstrated for security.
-
-For API aggregation, the Gateway will provide a central endpoint for HDFS,
-Templeton and Oozie APIs for each cluster.
-
-Future Milestone releases will extend these capabilities with additional
-authentication, identity assertion, API aggregation and eventually management
-capabilities.
-
-------------------------------------------------------------------------------
-Changes
-------------------------------------------------------------------------------
-Please see the CHANGES file.
-
-------------------------------------------------------------------------------
-Known Issues
-------------------------------------------------------------------------------
-Please see the ISSUES file.
-
-------------------------------------------------------------------------------
-Installation
-------------------------------------------------------------------------------
-Please see the INSTALL file or the Apache Knox Gateway website.
-http://knox.incubator.apache.org/getting-started.html
-
-------------------------------------------------------------------------------
-Examples
-------------------------------------------------------------------------------
-Please see the Apache Knox Gateway website for detailed examples.
-http://knox.incubator.apache.org/examples.html
-
-------------------------------------------------------------------------------
-Filing bugs
-------------------------------------------------------------------------------
-Currently we do not have Jira setup for Knox. Therefore if you find an issue
-please send an email to the Knox user list (user AT knox.incubator.apache.org)
-with a subject prefix of [BUG] describing the issue. Please include the
-results of this command in the email.
-
- java -jar bin/gateway-${gateway-version}.jar -version
-
-in the Environment section. Also include the version of Hadoop being used.
-
-One we have Jira setup the email archive will be reviewed and Jira issues
-created for each bug.
-
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/assembly.xml
----------------------------------------------------------------------
diff --git a/gateway-release/assembly.xml b/gateway-release/assembly.xml
deleted file mode 100644
index 7e3574c..0000000
--- a/gateway-release/assembly.xml
+++ /dev/null
@@ -1,85 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- 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.
--->
-<assembly>
- <id>bin</id>
- <formats>
- <format>zip</format>
- <format>tar.gz</format>
- </formats>
- <fileSets>
- <fileSet>
- <directory></directory>
- <outputDirectory></outputDirectory>
- <includes>
- <include>**</include>
- </includes>
- <excludes>
- <exclude>src/**</exclude>
- <exclude>target/**</exclude>
- <exclude>**/assembly.xml</exclude>
- <exclude>**/pom.xml</exclude>
- <exclude>**/.idea/**</exclude>
- <exclude>**/*.iml</exclude>
- <exclude>**/.project</exclude>
- <exclude>**/.settings/**</exclude>
- </excludes>
- </fileSet>
- </fileSets>
- <dependencySets>
- <dependencySet>
- <outputDirectory>dep</outputDirectory>
- <excludes>
- <exclude>maven-test:*</exclude>
- </excludes>
- </dependencySet>
- <dependencySet>
- <useProjectArtifact>false</useProjectArtifact>
- <outputDirectory>lib</outputDirectory>
- <includes>
- <include>${gateway-group}:*</include>
- </includes>
- <excludes>
- <exclude>${gateway-group}:gateway-util-launcher</exclude>
- <exclude>${gateway-group}:gateway-server-launcher</exclude>
- <exclude>${gateway-group}:gateway-shell-launcher</exclude>
- <exclude>${gateway-group}:gateway-test-ldap-launcher</exclude>
- </excludes>
- </dependencySet>
- <dependencySet>
- <outputDirectory>bin</outputDirectory>
- <outputFileNameMapping>gateway.jar</outputFileNameMapping>
- <includes>
- <include>${gateway-group}:gateway-server-launcher</include>
- </includes>
- </dependencySet>
- <dependencySet>
- <outputDirectory>bin</outputDirectory>
- <outputFileNameMapping>shell.jar</outputFileNameMapping>
- <includes>
- <include>${gateway-group}:gateway-shell-launcher</include>
- </includes>
- </dependencySet>
- <dependencySet>
- <outputDirectory>bin</outputDirectory>
- <outputFileNameMapping>ldap.jar</outputFileNameMapping>
- <includes>
- <include>${gateway-group}:gateway-test-ldap-launcher</include>
- </includes>
- </dependencySet>
- </dependencySets>
-</assembly>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/conf/README
----------------------------------------------------------------------
diff --git a/gateway-release/conf/README b/gateway-release/conf/README
deleted file mode 100644
index 68359c7..0000000
--- a/gateway-release/conf/README
+++ /dev/null
@@ -1 +0,0 @@
-THIS IS THE DIRECTORY WHERE YOU PLACE COPY OR SAVE THE gateway-site.xml and users.ldif FILE
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/conf/gateway-site.xml
----------------------------------------------------------------------
diff --git a/gateway-release/conf/gateway-site.xml b/gateway-release/conf/gateway-site.xml
deleted file mode 100644
index 76eaedc..0000000
--- a/gateway-release/conf/gateway-site.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-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.
--->
-<configuration>
-
- <property>
- <name>gateway.port</name>
- <value>8443</value>
- <description>The HTTP port for the Gateway.</description>
- </property>
-
- <property>
- <name>gateway.path</name>
- <value>gateway</value>
- <description>The default context path for the gateway.</description>
- </property>
-
- <property>
- <name>gateway.gateway.conf.dir</name>
- <value>deployments</value>
- <description>The directory within GATEWAY_HOME that contains gateway topology files and deployments.</description>
- </property>
-
-</configuration>
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/conf/log4j.properties
----------------------------------------------------------------------
diff --git a/gateway-release/conf/log4j.properties b/gateway-release/conf/log4j.properties
deleted file mode 100644
index ccde8c4..0000000
--- a/gateway-release/conf/log4j.properties
+++ /dev/null
@@ -1,29 +0,0 @@
-# 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.
-
-log4j.rootLogger=ERROR, stdout
-
-log4j.appender.stdout=org.apache.log4j.ConsoleAppender
-log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
-log4j.appender.stdout.layout.ConversionPattern=%d{yy/MM/dd HH:mm:ss} %p %c{2}: %m%n
-
-log4j.logger.org.apache.hadoop.gateway=INFO
-
-#log4j.logger.org.eclipse.jetty=ERROR
-#log4j.logger.org.apache.shiro=DEBUG
-#log4j.logger.org.apache.http=DEBUG
-#log4j.logger.org.apache.http.client=DEBUG
-#log4j.logger.org.apache.http.wire=DEBUG
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/conf/users.ldif
----------------------------------------------------------------------
diff --git a/gateway-release/conf/users.ldif b/gateway-release/conf/users.ldif
deleted file mode 100644
index 5b4b772..0000000
--- a/gateway-release/conf/users.ldif
+++ /dev/null
@@ -1,62 +0,0 @@
-# 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.
-
-version: 1
-
-dn: ou=people,dc=hadoop,dc=apache,dc=org
-objectclass:top
-objectclass:organizationalUnit
-ou: people
-
-dn: uid=hdfs,ou=people,dc=hadoop,dc=apache,dc=org
-objectclass:top
-objectclass:person
-objectclass:organizationalPerson
-objectclass:inetOrgPerson
-cn: HDFS
-sn: HDFS
-uid: hdfs
-userPassword:hdfs-password
-
-dn: uid=mapred,ou=people,dc=hadoop,dc=apache,dc=org
-objectclass:top
-objectclass:person
-objectclass:organizationalPerson
-objectclass:inetOrgPerson
-cn: MapReduce
-sn: MapReduce
-uid: mapred
-userPassword:mapred-password
-
-dn: uid=hive,ou=people,dc=hadoop,dc=apache,dc=org
-objectclass:top
-objectclass:person
-objectclass:organizationalPerson
-objectclass:inetOrgPerson
-cn: Hive
-sn: Hive
-uid: hive
-userPassword:hive-password
-
-dn: uid=hcat,ou=people,dc=hadoop,dc=apache,dc=org
-objectclass:top
-objectclass:person
-objectclass:organizationalPerson
-objectclass:inetOrgPerson
-cn: HCat
-sn: HCat
-uid: hcat
-userPassword:hcat-password
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/deployments/README
----------------------------------------------------------------------
diff --git a/gateway-release/deployments/README b/gateway-release/deployments/README
deleted file mode 100644
index 6588a11..0000000
--- a/gateway-release/deployments/README
+++ /dev/null
@@ -1 +0,0 @@
-THIS IS THE DIRECTORY WHERE YOU COPY OR SAVE CLUSTER TOPOLOGY DEPLOYMENT DESCRIPTOR FILES
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/deployments/sample.xml
----------------------------------------------------------------------
diff --git a/gateway-release/deployments/sample.xml b/gateway-release/deployments/sample.xml
deleted file mode 100644
index 616c57e..0000000
--- a/gateway-release/deployments/sample.xml
+++ /dev/null
@@ -1,60 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--
- 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.
--->
-<topology>
-
- <gateway>
- <provider>
- <role>authentication</role>
- <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>
- </gateway>
-
- <service>
- <role>NAMENODE</role>
- <url>http://vm:50070/webhdfs/v1</url>
- </service>
- <service>
- <role>TEMPLETON</role>
- <url>http://vm:50111/templeton/v1</url>
- </service>
- <service>
- <role>OOZIE</role>
- <url>http://vm:11000/oozie</url>
- </service>
-
-</topology>
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/ext/README
----------------------------------------------------------------------
diff --git a/gateway-release/ext/README b/gateway-release/ext/README
deleted file mode 100644
index 9eb0ca5..0000000
--- a/gateway-release/ext/README
+++ /dev/null
@@ -1 +0,0 @@
-THIS DIRECTORY IS WHERE JARS AND CLASSES CONTAINING CUSTOM EXTENSIONS CAN BE PLACED
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/home/CHANGES
----------------------------------------------------------------------
diff --git a/gateway-release/home/CHANGES b/gateway-release/home/CHANGES
new file mode 100644
index 0000000..40a6ddc
--- /dev/null
+++ b/gateway-release/home/CHANGES
@@ -0,0 +1,11 @@
+------------------------------------------------------------------------------
+Changes v0.1.0 - v0.2.0
+------------------------------------------------------------------------------
+HTTPS Support (Client side)
+Oozie Support
+Protected DataNode URL query strings
+Pluggable Identity Asserters
+Principal Mapping
+URL Rewriting Enhancements
+KnoxShell Client DSL
+
http://git-wip-us.apache.org/repos/asf/incubator-knox/blob/800736a8/gateway-release/home/DISCLAIMER
----------------------------------------------------------------------
diff --git a/gateway-release/home/DISCLAIMER b/gateway-release/home/DISCLAIMER
new file mode 100644
index 0000000..e6af5c0
--- /dev/null
+++ b/gateway-release/home/DISCLAIMER
@@ -0,0 +1,15 @@
+Apache Knox is an effort undergoing incubation at the Apache Software
+Foundation (ASF), sponsored by the Apache Incubator PMC.
+
+Incubation is required of all newly accepted projects until a further review
+indicates that the infrastructure, communications, and decision making process
+have stabilized in a manner consistent with other successful ASF projects.
+
+While incubation status is not necessarily a reflection of the completeness
+or stability of the code, it does indicate that the project has yet to be
+fully endorsed by the ASF.
+
+For more information about the incubation status of the Apache Knox project you
+can go to the following page:
+
+http://incubator.apache.org/projects/knox.html
\ No newline at end of file