Author: krisden
Date: Fri Mar 13 21:07:56 2020
New Revision: 1875176
URL: http://svn.apache.org/viewvc?rev=1875176&view=rev
Log:
KNOX-2293 - Mutual TLS docs can be improved
Modified:
knox/site/books/knox-0-12-0/user-guide.html
knox/site/books/knox-0-13-0/user-guide.html
knox/site/books/knox-0-14-0/user-guide.html
knox/site/books/knox-1-0-0/user-guide.html
knox/site/books/knox-1-1-0/user-guide.html
knox/site/books/knox-1-2-0/user-guide.html
knox/site/books/knox-1-3-0/user-guide.html
knox/site/books/knox-1-4-0/user-guide.html
knox/trunk/books/0.10.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.11.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.12.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.13.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.14.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.6.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.7.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.8.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.9.0/config_mutual_authentication_ssl.md
knox/trunk/books/0.9.1/config_mutual_authentication_ssl.md
knox/trunk/books/1.0.0/config_mutual_authentication_ssl.md
knox/trunk/books/1.1.0/config_mutual_authentication_ssl.md
knox/trunk/books/1.2.0/config_mutual_authentication_ssl.md
knox/trunk/books/1.3.0/config_mutual_authentication_ssl.md
knox/trunk/books/1.4.0/config_mutual_authentication_ssl.md
Modified: knox/site/books/knox-0-12-0/user-guide.html
URL:
http://svn.apache.org/viewvc/knox/site/books/knox-0-12-0/user-guide.html?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/site/books/knox-0-12-0/user-guide.html (original)
+++ knox/site/books/knox-0-12-0/user-guide.html Fri Mar 13 21:07:56 2020
@@ -3772,7 +3772,7 @@ APACHE_HOME/bin/apachectl -k stop
<p>See documentation in Client Details for KnoxShell init, list and destroy
for commands that leverage this token service for CLI sessions.</p>
<h3><a id="Mutual+Authentication+with+SSL">Mutual Authentication with SSL</a>
<a href="#Mutual+Authentication+with+SSL"><img
src="markbook-section-link.png"/></a></h3>
<p>To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.</p>
-<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.</p>
+<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be
refused.</p>
<p>The following table describes the configuration elements related to mutual
authentication and their defaults:</p>
<table>
<thead>
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=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/site/books/knox-0-13-0/user-guide.html (original)
+++ knox/site/books/knox-0-13-0/user-guide.html Fri Mar 13 21:07:56 2020
@@ -3826,7 +3826,7 @@ APACHE_HOME/bin/apachectl -k stop
<p>See documentation in Client Details for KnoxShell init, list and destroy
for commands that leverage this token service for CLI sessions.</p>
<h3><a id="Mutual+Authentication+with+SSL">Mutual Authentication with SSL</a>
<a href="#Mutual+Authentication+with+SSL"><img
src="markbook-section-link.png"/></a></h3>
<p>To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.</p>
-<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.</p>
+<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be
refused.</p>
<p>The following table describes the configuration elements related to mutual
authentication and their defaults:</p>
<table>
<thead>
Modified: knox/site/books/knox-0-14-0/user-guide.html
URL:
http://svn.apache.org/viewvc/knox/site/books/knox-0-14-0/user-guide.html?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/site/books/knox-0-14-0/user-guide.html (original)
+++ knox/site/books/knox-0-14-0/user-guide.html Fri Mar 13 21:07:56 2020
@@ -4852,7 +4852,7 @@ APACHE_HOME/bin/apachectl -k stop
<p>See documentation in Client Details for KnoxShell init, list and destroy
for commands that leverage this token service for CLI sessions.</p>
<h3><a id="Mutual+Authentication+with+SSL">Mutual Authentication with SSL</a>
<a href="#Mutual+Authentication+with+SSL"><img
src="markbook-section-link.png"/></a></h3>
<p>To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.</p>
-<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.</p>
+<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be
refused.</p>
<p>The following table describes the configuration elements related to mutual
authentication and their defaults:</p>
<table>
<thead>
Modified: knox/site/books/knox-1-0-0/user-guide.html
URL:
http://svn.apache.org/viewvc/knox/site/books/knox-1-0-0/user-guide.html?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/site/books/knox-1-0-0/user-guide.html (original)
+++ knox/site/books/knox-1-0-0/user-guide.html Fri Mar 13 21:07:56 2020
@@ -4860,7 +4860,7 @@ APACHE_HOME/bin/apachectl -k stop
<p>See documentation in Client Details for KnoxShell init, list and destroy
for commands that leverage this token service for CLI sessions.</p>
<h3><a id="Mutual+Authentication+with+SSL">Mutual Authentication with SSL</a>
<a href="#Mutual+Authentication+with+SSL"><img
src="markbook-section-link.png"/></a></h3>
<p>To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.</p>
-<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.</p>
+<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be
refused.</p>
<p>The following table describes the configuration elements related to mutual
authentication and their defaults:</p>
<table>
<thead>
Modified: knox/site/books/knox-1-1-0/user-guide.html
URL:
http://svn.apache.org/viewvc/knox/site/books/knox-1-1-0/user-guide.html?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/site/books/knox-1-1-0/user-guide.html (original)
+++ knox/site/books/knox-1-1-0/user-guide.html Fri Mar 13 21:07:56 2020
@@ -5029,7 +5029,7 @@ APACHE_HOME/bin/apachectl -k stop
<p>See documentation in Client Details for KnoxShell init, list and destroy
for commands that leverage this token service for CLI sessions.</p>
<h3><a id="Mutual+Authentication+with+SSL">Mutual Authentication with SSL</a>
<a href="#Mutual+Authentication+with+SSL"><img
src="markbook-section-link.png"/></a></h3>
<p>To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just IP address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.</p>
-<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.</p>
+<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be
refused.</p>
<p>The following table describes the configuration elements related to mutual
authentication and their defaults:</p>
<table>
<thead>
Modified: knox/site/books/knox-1-2-0/user-guide.html
URL:
http://svn.apache.org/viewvc/knox/site/books/knox-1-2-0/user-guide.html?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/site/books/knox-1-2-0/user-guide.html (original)
+++ knox/site/books/knox-1-2-0/user-guide.html Fri Mar 13 21:07:56 2020
@@ -5044,7 +5044,7 @@ APACHE_HOME/bin/apachectl -k stop
<p>See documentation in Client Details for KnoxShell init, list and destroy
for commands that leverage this token service for CLI sessions.</p>
<h3><a id="Mutual+Authentication+with+SSL">Mutual Authentication with SSL</a>
<a href="#Mutual+Authentication+with+SSL"><img
src="markbook-section-link.png"/></a></h3>
<p>To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just IP address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.</p>
-<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.</p>
+<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be
refused.</p>
<p>The following table describes the configuration elements related to mutual
authentication and their defaults:</p>
<table>
<thead>
Modified: knox/site/books/knox-1-3-0/user-guide.html
URL:
http://svn.apache.org/viewvc/knox/site/books/knox-1-3-0/user-guide.html?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/site/books/knox-1-3-0/user-guide.html (original)
+++ knox/site/books/knox-1-3-0/user-guide.html Fri Mar 13 21:07:56 2020
@@ -5297,7 +5297,7 @@ APACHE_HOME/bin/apachectl -k stop
<p>See documentation in Client Details for KnoxShell init, list and destroy
for commands that leverage this token service for CLI sessions.</p>
<h3><a id="Mutual+Authentication+with+SSL">Mutual Authentication with SSL</a>
<a href="#Mutual+Authentication+with+SSL"><img
src="markbook-section-link.png"/></a></h3>
<p>To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just IP address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.</p>
-<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.</p>
+<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be
refused.</p>
<p>The following table describes the configuration elements related to mutual
authentication and their defaults:</p>
<table>
<thead>
Modified: knox/site/books/knox-1-4-0/user-guide.html
URL:
http://svn.apache.org/viewvc/knox/site/books/knox-1-4-0/user-guide.html?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/site/books/knox-1-4-0/user-guide.html (original)
+++ knox/site/books/knox-1-4-0/user-guide.html Fri Mar 13 21:07:56 2020
@@ -5323,7 +5323,7 @@ APACHE_HOME/bin/apachectl -k stop
<p>See documentation in Client Details for KnoxShell init, list and destroy
for commands that leverage this token service for CLI sessions.</p>
<h3><a id="Mutual+Authentication+with+SSL">Mutual Authentication with SSL</a>
<a href="#Mutual+Authentication+with+SSL"><img
src="markbook-section-link.png"/></a></h3>
<p>To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just IP address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.</p>
-<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.</p>
+<p>This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be
refused.</p>
<p>The following table describes the configuration elements related to mutual
authentication and their defaults:</p>
<table>
<thead>
Modified: knox/trunk/books/0.10.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.10.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.10.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.10.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.11.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.11.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.11.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.11.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.12.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.12.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.12.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.12.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.13.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.13.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.13.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.13.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.14.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.14.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.14.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.14.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.6.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.6.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.6.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.6.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.7.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.7.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.7.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.7.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.8.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.8.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.8.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.8.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.9.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.9.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.9.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.9.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/0.9.1/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/0.9.1/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/0.9.1/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/0.9.1/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/1.0.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/1.0.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/1.0.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/1.0.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just ip address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/1.1.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/1.1.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/1.1.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/1.1.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just IP address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/1.2.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/1.2.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/1.2.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/1.2.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just IP address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/1.3.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/1.3.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/1.3.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/1.3.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just IP address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
Modified: knox/trunk/books/1.4.0/config_mutual_authentication_ssl.md
URL:
http://svn.apache.org/viewvc/knox/trunk/books/1.4.0/config_mutual_authentication_ssl.md?rev=1875176&r1=1875175&r2=1875176&view=diff
==============================================================================
--- knox/trunk/books/1.4.0/config_mutual_authentication_ssl.md (original)
+++ knox/trunk/books/1.4.0/config_mutual_authentication_ssl.md Fri Mar 13
21:07:56 2020
@@ -19,7 +19,7 @@
To establish a stronger trust relationship between client and server, we
provide mutual authentication with SSL via client certs. This is particularly
useful in providing additional validation for Preauthenticated SSO with HTTP
Headers. Rather than just IP address validation, connections will only be
accepted by Knox from clients presenting trusted certificates.
-This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the gateway instance with
mutual authentication enabled will require incoming connections to present
trusted client certificates during the SSL handshake. Otherwise, connections
will be refused.
+This behavior is configured for the entire gateway instance within the
gateway-site.xml file. All topologies deployed within the configured gateway
instance will require incoming connections to present trusted client
certificates during the SSL handshake. Otherwise, connections will be refused.
The following table describes the configuration elements related to mutual
authentication and their defaults:
