Author: buildbot
Date: Tue Nov 25 11:01:12 2014
New Revision: 930421
Log:
Staging update by buildbot for ace
Modified:
websites/staging/ace/trunk/content/ (props changed)
websites/staging/ace/trunk/content/docs/using-basic-auth.html
Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 25 11:01:12 2014
@@ -1 +1 @@
-1641565
+1641566
Modified: websites/staging/ace/trunk/content/docs/using-basic-auth.html
==============================================================================
--- websites/staging/ace/trunk/content/docs/using-basic-auth.html (original)
+++ websites/staging/ace/trunk/content/docs/using-basic-auth.html Tue Nov 25
11:01:12 2014
@@ -101,9 +101,18 @@
<p><a href="/"><i class='icon-home'></i> Home</a> » <a
href="/docs/">Docs</a></p>
<h1>ACE Authentication</h1>
<div class="clear"></div>
- <div id="content"><div class="toc">
+ <div id="content"><p>When provisioning software (partly) to targets, one
has to rely upon the trustworthiness
+of both the network and the target. Even if everything is under your control
and
+governance, one cannot entirely be sure that unwanted access takes place. A
first step in
+order to prevent unwanted access is <em>authentication</em>, which gives you
the ability to
+verify the identity of someone. Once the identity is known, one can apply
<em>authorization</em>
+in order to determine what actions are allowed and which are not. In this
article, the
+recently added authentication layer of ACE is explained in more depth and how
to configure
+authentication to your situation.</p>
+<p>More details on the design of the authentication mechanism in ACE can be
found in the
+<a href="/docs/design/authentication-design.mdtext">design
documentation</a>.</p>
+<div class="toc">
<ul>
-<li><a href="#introduction">Introduction</a></li>
<li><a href="#configuring-authentication">Configuring authentication</a><ul>
<li><a href="#remote-services">Remote services</a></li>
<li><a href="#the-connection-factory">The connection factory</a></li>
@@ -115,17 +124,6 @@
<li><a href="#notes">Notes</a></li>
</ul>
</div>
-<h2 id="introduction">Introduction</h2>
-<p>When provisioning software (partly) to targets, one has to rely upon the
trustworthiness
-of both the network and the target. Even if everything is under your control
and
-governance, one cannot entirely be sure that unwanted access takes place. A
first step in
-order to prevent unwanted access is <em>authentication</em>, which gives you
the ability to
-verify the identity of someone. Once the identity is known, one can apply
<em>authorization</em>
-in order to determine what actions are allowed and which are not. In this
article, the
-recently added authentication layer of ACE is explained in more depth and how
to configure
-authentication to your situation.
-More details on the design of the authentication mechanism in ACE can be found
in the
-<a href="/docs/design/authentication-design.mdtext">design
documentation</a>.</p>
<h2 id="configuring-authentication">Configuring authentication</h2>
<p>By default, ACE has no form of authentication enabled. While this is
sufficient for
demonstration purposes, you might want to change this prior to putting ACE into
