You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by gm...@apache.org on 2019/07/30 13:56:46 UTC
[qpid-dispatch] branch master updated: NO-JIRA - Fix typo and minor
issues in doc. This closes #547.
This is an automated email from the ASF dual-hosted git repository.
gmurthy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/qpid-dispatch.git
The following commit(s) were added to refs/heads/master by this push:
new 1030120 NO-JIRA - Fix typo and minor issues in doc. This closes #547.
1030120 is described below
commit 1030120cee7b8258f7f522ebec7c50d4d367da91
Author: Ben Hardesty <bh...@redhat.com>
AuthorDate: Fri Jul 26 15:25:36 2019 -0400
NO-JIRA - Fix typo and minor issues in doc. This closes #547.
---
docs/books/user-guide/authorization.adoc | 2 +-
.../modules/enabling-ssl-tls-client-authentication.adoc | 2 +-
docs/books/user-guide/modules/integrating-with-kerberos.adoc | 9 ++++++---
3 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/docs/books/user-guide/authorization.adoc b/docs/books/user-guide/authorization.adoc
index c0516e8..3eab5ff 100644
--- a/docs/books/user-guide/authorization.adoc
+++ b/docs/books/user-guide/authorization.adoc
@@ -229,7 +229,7 @@ A list of AMQP target addresses from which users in this group may send messages
+
The advanced user group settings enable you to define resource limits based on the AMQP connection open, session begin, and link attach phases of the connection. For more information, see link:{qdrouterdConfManPageUrl}#_vhost[vhost^] in the `qdrouterd.conf` man page.
-[id='']
+[id='configuring-resource-limits-outgoing-connections']
=== Configuring Resource Limits for Outgoing Connections
If the router establishes an outgoing connection to an external AMQP container (such as a client or broker), you can restrict the resources that the external container can access on the router by configuring a connector vhost policy.
diff --git a/docs/books/user-guide/modules/enabling-ssl-tls-client-authentication.adoc b/docs/books/user-guide/modules/enabling-ssl-tls-client-authentication.adoc
index 235d97b..78bbb34 100644
--- a/docs/books/user-guide/modules/enabling-ssl-tls-client-authentication.adoc
+++ b/docs/books/user-guide/modules/enabling-ssl-tls-client-authentication.adoc
@@ -24,7 +24,7 @@ under the License
[id='enabling-ssl-tls-client-authentication-{context}']
= Enabling SSL/TLS client authentication
-In additional to SSL/TLS encryption, you can also use SSL/TLS to authenticate an incoming connection from a client. With this method, a clients must present its own X.509 certificate to the router, which the router uses to verify the client's identity.
+In addition to SSL/TLS encryption, you can also use SSL/TLS to authenticate an incoming connection from a client. With this method, a clients must present its own X.509 certificate to the router, which the router uses to verify the client's identity.
.Prerequisites
diff --git a/docs/books/user-guide/modules/integrating-with-kerberos.adoc b/docs/books/user-guide/modules/integrating-with-kerberos.adoc
index 4385b26..9d5fd9e 100644
--- a/docs/books/user-guide/modules/integrating-with-kerberos.adoc
+++ b/docs/books/user-guide/modules/integrating-with-kerberos.adoc
@@ -54,10 +54,13 @@ mech_list: ANONYMOUS DIGEST-MD5 EXTERNAL PLAIN GSSAPI
--
. Verify the following:
-** The `mech_list` attribute contains the `GSSAPI` mechanism.
-** The `keytab` attribute points to the location of the keytab file.
++
+--
+* The `mech_list` attribute contains the `GSSAPI` mechanism.
+* The `keytab` attribute points to the location of the keytab file.
+--
-include::{FragmentDir}/fragment-router-open-config-file-step.adoc[]
+. Open the `{RouterConfigFile}` configuration file.
. In the `router` section, specify the path to the SASL configuration file.
+
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org