Author: buildbot
Date: Tue Nov 25 11:19:28 2014
New Revision: 930426
Log:
Staging update by buildbot for ace
Modified:
websites/staging/ace/trunk/content/ (props changed)
websites/staging/ace/trunk/content/docs/using-client-certificates.html
Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 25 11:19:28 2014
@@ -1 +1 @@
-1641576
+1641577
Modified: websites/staging/ace/trunk/content/docs/using-client-certificates.html
==============================================================================
--- websites/staging/ace/trunk/content/docs/using-client-certificates.html (original)
+++ websites/staging/ace/trunk/content/docs/using-client-certificates.html Tue Nov 25 11:19:28
2014
@@ -109,7 +109,7 @@
<li><a href="#using-multiple-different-keystores">Using multiple different keystores</a></li>
</ul>
</li>
-<li><a href="#faq">FAQ</a></li>
+<li><a href="#troubleshooting">Troubleshooting</a></li>
</ul>
</div>
<h2 id="introduction">Introduction</h2>
@@ -245,7 +245,10 @@ configuration to the <tt>ConnectionFacto
relations to be established.</p>
<p>Be sure that in order to let ACE correctly map certificates to users, you need to
install
the <tt>ClientCertAuthenticationProcessor</tt> as additional authentication processor!
</p>
-<h2 id="faq">FAQ</h2>
+<h2 id="troubleshooting">Troubleshooting</h2>
+<p>If after configuring the authentication of ACE things no longer work, it can be
hard to
+find the exact cause of this. In this section, some pointers are given to help you to find
+the probably cause of the problem.</p>
<dl>
<dt>How should I name the certificates?</dt>
<dd>One should use the hostname of the calling side as common name (CN) of the certificate's
|