svn commit: r1011805 - in /websites/staging/directory/trunk/content: ./ fortress/testimonials.html

[bu...@apache.org]

Author: buildbot
Date: Sun May  7 17:51:37 2017
New Revision: 1011805

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/fortress/testimonials.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun May  7 17:51:37 2017
@@ -1 +1 @@
-1794233
+1794235

Modified: websites/staging/directory/trunk/content/fortress/testimonials.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/testimonials.html (original)
+++ websites/staging/directory/trunk/content/fortress/testimonials.html Sun May  7 17:51:37 2017
@@ -173,7 +173,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>This work was contributed by Yudhi Karunia Surtan of PT. Global Digital Niaga (blibli.com).  Thanks to him and his team for their efforts in helping others use Fortress.</p>
 <h2 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">&para;</a></h2>
 <p>This document contains an overview of the URL filtering mechanism.</p>
-<h3 id="destailed-description-of-the-project">Destailed description of the project<a class="headerlink" href="#destailed-description-of-the-project" title="Permanent link">&para;</a></h3>
+<h3 id="detailed-description-of-the-project">Detailed description of the project<a class="headerlink" href="#detailed-description-of-the-project" title="Permanent link">&para;</a></h3>
 <p>I created this solution because at the time I was looking an IAM and SSO solution, and there were no open source solution to provide everything that I required.</p>
 <p>Basically, the idea is, I wanted to have a framework where the developer doesn't need to programmatically make authorization calls, use annotation or any other kind of “if condition” statements, in their code. With this solution, I'm can have a declarative mechanism capable of dynamic authorization decisions, even if the user hasn't been logged in or has the the proper role activated.  This is because the authorization has been centralized at the server and that server can activate and deactivate user roles that are needed to access the runtime environment.</p>
 <p>I searched across all available open source solutions and finally decided to use Apereo CAS and Apache Fortress as the combined solution. Apereo CAS does the authentication and Apache Fortress will handle the authorization.</p>
@@ -188,12 +188,10 @@ h2:hover > .headerlink, h3:hover > .head
 <li>Spring Framework -&gt; 4.2.x-RELEASE</li>
 </ul>
 <p>There are two types of development required, one on server side and other on the client, which is then used by my team for managing security within their own web applications:</p>
-<p>CAS Server side development:
-  - Create own implementation for AbstractUsernamePasswordAuthenticationHandler
-  - Implement Ignite Service Registry for CAS</p>
-<p>CAS Client side development:
-  - Create own implementation for WebExpressionVoter
-  - Create own implementation for CasAuthenticationProvider</p>
+<ol>
+<li>CAS Server side development: Includes creating own implementation for AbstractUsernamePasswordAuthenticationHandler and implemening an Apache Ignite Service Registry for CAS</li>
+<li>CAS Client side development: Includes create own implementation for WebExpressionVoter and CasAuthenticationProvider</li>
+</ol>
 <h2 id="code-descriptions">Code Descriptions<a class="headerlink" href="#code-descriptions" title="Permanent link">&para;</a></h2>
 <p>The following sections contain code and xml snippets describing how the CAS and Fortress integration was accomplished.</p>
 <h3 id="server-side-development">Server side development:<a class="headerlink" href="#server-side-development" title="Permanent link">&para;</a></h3>