Author: more Date: Tue Jun 6 15:39:04 2017 New Revision: 1797795 URL: http://svn.apache.org/viewvc?rev=1797795&view=rev Log: KNOX-946 - Spelling fix (Colm O hEigeartaigh via Sandeep More) Modified: knox/site/books/knox-0-13-0/user-guide.html knox/site/index.html knox/site/issue-tracking.html knox/site/license.html knox/site/mail-lists.html knox/site/project-info.html knox/site/team-list.html knox/trunk/books/0.13.0/config_sso_cookie_provider.md knox/trunk/books/0.13.0/service_storm.md Modified: knox/site/books/knox-0-13-0/user-guide.html URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-13-0/user-guide.html?rev=1797795&r1=1797794&r2=1797795&view=diff ============================================================================== --- knox/site/books/knox-0-13-0/user-guide.html (original) +++ knox/site/books/knox-0-13-0/user-guide.html Tue Jun 6 15:39:04 2017 @@ -2614,7 +2614,7 @@ APACHE_HOME/bin/apachectl -k stop N/A -

JWT Provider

Overview

The JWT federation provider accepts JWT tokens as Bearer tokens within the Authorization header of the incoming request. Upon successfully extracting and verify the token, the request is then processed on behalf of the user represented by the JWT token.

This provider is closely related to the Knox Token Service and is essentially the provider that is used to consume the tokens issued by the Knox Token Service.

Typical deployments have the KnoxToken service defined in a topology such as sandbox.xml that authenticates users based on username and password which as with the ShiroProvider. They also have a topology dedicated to clients that wish to use KnoxTokens to access Hadoop resources through Knox.

The following provider configuration can be u sed within such a topology.

+

JWT Provider

Overview

The JWT federation provider accepts JWT tokens as Bearer tokens within the Authorization header of the incoming request. Upon successfully extracting and verifying the token, the request is then processed on behalf of the user represented by the JWT token.

This provider is closely related to the Knox Token Service and is essentially the provider that is used to consume the tokens issued by the Knox Token Service.

Typical deployments have the KnoxToken service defined in a topology such as sandbox.xml that authenticates users based on username and password which as with the ShiroProvider. They also have a topology dedicated to clients that wish to use KnoxTokens to access Hadoop resources through Knox.

The following provider configuration can b e used within such a topology.

<provider>
    <role>federation</role>
    <name>JWTProvider</name>
@@ -5009,7 +5009,7 @@ The contents of the state-killed.json fi
 
 
 curl -ikv -u guest:guest-password -H Content-Type:application/json -X PUT -T state-killed.json 'https://localhost:8443/gateway/sandbox/resourcemanager/v1/cluster/apps/{application_id}/state'
-

Storm

Storm is a distributed realtime computation system. Storm exposes REST APIs for UI functionality that can be used for retrieving metrics data and configuration information as well as management operations such as starting or stopping topologies.

The docs for this can be found here

https://github.com/apache/storm/blob/master/docs/documentation/ui-rest-api.md

To enable this functionality, a topology file needs to have the following configuration:

+

Storm

Storm is a distributed realtime computation system. Storm exposes REST APIs for UI functionality that can be used for retrieving metrics data and configuration information as well as management operations such as starting or stopping topologies.

The docs for this can be found here

https://github.com/apache/storm/blob/master/docs/STORM-UI-REST-API.md

To enable this functionality, a topology file needs to have the following configuration:

<service>
     <role>STORM</role>
     <url>http://<hostname>:<port></url>

Modified: knox/site/index.html
URL: http://svn.apache.org/viewvc/knox/site/index.html?rev=1797795&r1=1797794&r2=1797795&view=diff
==============================================================================
--- knox/site/index.html (original)
+++ knox/site/index.html Tue Jun  6 15:39:04 2017
@@ -1,13 +1,13 @@
 
 
 
   
     
     
-    
+    
     
     Knox Gateway – REST API and Application Gateway for the Apache Hadoop Ecosystem
     
@@ -58,7 +58,7 @@
               
                 
                     
-                  
  • Last Published: 2017-06-02
  • +
  • Last Published: 2017-06-06
  • Modified: knox/site/issue-tracking.html URL: http://svn.apache.org/viewvc/knox/site/issue-tracking.html?rev=1797795&r1=1797794&r2=1797795&view=diff ============================================================================== --- knox/site/issue-tracking.html (original) +++ knox/site/issue-tracking.html Tue Jun 6 15:39:04 2017 @@ -1,13 +1,13 @@ - + Knox Gateway – Issue Tracking @@ -58,7 +58,7 @@ -
  • Last Published: 2017-06-02
  • +
  • Last Published: 2017-06-06
  • Modified: knox/site/license.html URL: http://svn.apache.org/viewvc/knox/site/license.html?rev=1797795&r1=1797794&r2=1797795&view=diff ============================================================================== --- knox/site/license.html (original) +++ knox/site/license.html Tue Jun 6 15:39:04 2017 @@ -1,13 +1,13 @@ - + Knox Gateway – Project License @@ -58,7 +58,7 @@ -
  • Last Published: 2017-06-02
  • +
  • Last Published: 2017-06-06
  • Modified: knox/site/mail-lists.html URL: http://svn.apache.org/viewvc/knox/site/mail-lists.html?rev=1797795&r1=1797794&r2=1797795&view=diff ============================================================================== --- knox/site/mail-lists.html (original) +++ knox/site/mail-lists.html Tue Jun 6 15:39:04 2017 @@ -1,13 +1,13 @@ - + Knox Gateway – Project Mailing Lists @@ -58,7 +58,7 @@ -
  • Last Published: 2017-06-02
  • +
  • Last Published: 2017-06-06
  • Modified: knox/site/project-info.html URL: http://svn.apache.org/viewvc/knox/site/project-info.html?rev=1797795&r1=1797794&r2=1797795&view=diff ============================================================================== --- knox/site/project-info.html (original) +++ knox/site/project-info.html Tue Jun 6 15:39:04 2017 @@ -1,13 +1,13 @@ - + Knox Gateway – Project Information @@ -58,7 +58,7 @@ -
  • Last Published: 2017-06-02
  • +
  • Last Published: 2017-06-06
  • Modified: knox/site/team-list.html URL: http://svn.apache.org/viewvc/knox/site/team-list.html?rev=1797795&r1=1797794&r2=1797795&view=diff ============================================================================== --- knox/site/team-list.html (original) +++ knox/site/team-list.html Tue Jun 6 15:39:04 2017 @@ -1,13 +1,13 @@ - + Knox Gateway – Team list @@ -58,7 +58,7 @@ -
  • Last Published: 2017-06-02
  • +
  • Last Published: 2017-06-06
  • Modified: knox/trunk/books/0.13.0/config_sso_cookie_provider.md URL: http://svn.apache.org/viewvc/knox/trunk/books/0.13.0/config_sso_cookie_provider.md?rev=1797795&r1=1797794&r2=1797795&view=diff ============================================================================== --- knox/trunk/books/0.13.0/config_sso_cookie_provider.md (original) +++ knox/trunk/books/0.13.0/config_sso_cookie_provider.md Tue Jun 6 15:39:04 2017 @@ -75,7 +75,7 @@ sso.authentication.provider.url|Required ### JWT Provider ### #### Overview #### -The JWT federation provider accepts JWT tokens as Bearer tokens within the Authorization header of the incoming request. Upon successfully extracting and verify the token, the request is then processed on behalf of the user represented by the JWT token. +The JWT federation provider accepts JWT tokens as Bearer tokens within the Authorization header of the incoming request. Upon successfully extracting and verifying the token, the request is then processed on behalf of the user represented by the JWT token. This provider is closely related to the Knox Token Service and is essentially the provider that is used to consume the tokens issued by the Knox Token Service. @@ -103,4 +103,4 @@ Name | Description | Default ---------|----------- knox.token.audiences|Optional parameter. This parameter allows the administrator to constrain the use of tokens on this endpoint to those that have tokens with at least one of the configured audience claims. These claims have associated configuration within the KnoxToken service as well. This provides an interesting way to make sure that the token issued based on authentication to a particular LDAP server or other IdP is accepted but not others.|N/A -See the documentation for the Knox Token service for related details. \ No newline at end of file +See the documentation for the Knox Token service for related details. Modified: knox/trunk/books/0.13.0/service_storm.md URL: http://svn.apache.org/viewvc/knox/trunk/books/0.13.0/service_storm.md?rev=1797795&r1=1797794&r2=1797795&view=diff ============================================================================== --- knox/trunk/books/0.13.0/service_storm.md (original) +++ knox/trunk/books/0.13.0/service_storm.md Tue Jun 6 15:39:04 2017 @@ -22,7 +22,7 @@ retrieving metrics data and configuratio The docs for this can be found here -https://github.com/apache/storm/blob/master/docs/documentation/ui-rest-api.md +https://github.com/apache/storm/blob/master/docs/STORM-UI-REST-API.md To enable this functionality, a topology file needs to have the following configuration: