ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r814402 - in /websites/staging/ace/trunk/content: ./ dev-doc/design/ace-authentication.html
Date Wed, 25 Apr 2012 13:32:20 GMT
Author: buildbot
Date: Wed Apr 25 13:32:19 2012
New Revision: 814402

Staging update by buildbot for ace

    websites/staging/ace/trunk/content/   (props changed)

Propchange: websites/staging/ace/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr 25 13:32:19 2012
@@ -1 +1 @@

Modified: websites/staging/ace/trunk/content/dev-doc/design/ace-authentication.html
--- websites/staging/ace/trunk/content/dev-doc/design/ace-authentication.html (original)
+++ websites/staging/ace/trunk/content/dev-doc/design/ace-authentication.html Wed Apr 25 13:32:19
@@ -154,6 +154,28 @@
       <div class="clear"></div>
       <div id="content"><p><em>Enabling authentication in ACE</em></p>
 <p>last updated: April 25th, 2012</p>
+<div class="toc">
+<li><a href="#introduction">Introduction</a></li>
+<li><a href="#communication-paths">Communication paths</a></li>
+<li><a href="#authentication-design">Authentication design</a></li>
+<li><a href="#configuring-authentication">Configuring authentication</a><ul>
+<li><a href="#remote-services">Remote services</a></li>
+<li><a href="#configuring-authentication-for-remote-services">Configuring authentication
for remote services</a><ul>
+<li><a href="#service-configuration">Service configuration</a></li>
+<li><a href="#implemention">Implemention</a></li>
+<li><a href="#configuring-the-connection-factory">Configuring the connection
+<li><a href="#configuring-the-management-agent">Configuring the management agent</a></li>
+<li><a href="#extending-the-authentication-mechanism">Extending the authentication
+<li><a href="#authentication-processors">Authentication processors</a></li>
 <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 some details on how extensions can be written for additional mechanisms are given. The
remainder of this article assumes the reader has basic knowledge of the principles behind
ACE, and has sufficient programming skills. For this article, the latest code of ACE (0.8.1-SNAPSHOT,
rev.1329269) was used.</p>

View raw message