Author: chirino
Date: Thu Mar 22 14:11:14 2012
New Revision: 1303791
URL: http://svn.apache.org/viewvc?rev=1303791&view=rev
Log:
Fixes APLO-169 : Documented how to configure the client auth mode in SSL
transports.
Modified:
activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md
Modified:
activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md
URL:
http://svn.apache.org/viewvc/activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md?rev=1303791&r1=1303790&r2=1303791&view=diff
==============================================================================
---
activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md
(original)
+++
activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md
Thu Mar 22 14:11:14 2012
@@ -586,7 +586,15 @@ The attributes that you can configure on
* `key_algorithm` : The key management algorithm, defaults to `SunX509`.
The SSL/TLS transport is an extension of the TCP transport and as such it
supports
-all the same URI options which the TCP transport supports.
+all the same URI options which the TCP transport supports plus the following:
+
+* `client_auth` : can be set to one of the following: `want`, `need` or
+ `none`. Defaults to `want`. If set to `need`, then the SSL connection
+ will not be accepted if the client does not provide a certificate that
+ is trusted by the key store. If set to `none`, then we will not request
+ the client to send his certificates. If set to `want`, then we will
+ request the client send his certficates but allow the connection to
+ continue even if the does not have any tusted certs.
#### Authentication
