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

[bu...@apache.org]

Author: buildbot
Date: Tue May  9 02:37:32 2017
New Revision: 1011894

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 Tue May  9 02:37:32 2017
@@ -1 +1 @@
-1794487
+1794488

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 Tue May  9 02:37:32 2017
@@ -178,7 +178,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>Basically, the idea was, I needed a framework where the developer didn't have to programmatically add authorization calls to their code, or use annotations, or any other kind of “if condition” statement. With this solution, I can have a declarative mechanism that is still capable of making advanced dynamic authorization decisions, even if the user hasn't been logged in before or has any of the proper roles activated to their session.  I can do this because I control the authorization and it has been centralized in the server, and that server can activate whatever user roles needed to to allow access to the runtime environment.</p>
 <p>I searched all available open source solutions and finally decided to combine Apereo CAS and Apache Fortress into a single solution. Apereo CAS does the authentication and Apache Fortress will handle authorization.</p>
 <p>I went this route because Apereo CAS is very good way to handle the Single Sign-On and Single Sign-Out problems, but it lacks authorization capabilities, because there aren't standardized solutions in that space yet. Apache Fortress is good at authorization because it uses standard RBAC. However, Apache Fortress doesn't have an SSO solution yet. That is why I think both should be combined because they complement each other.  Unfortunately, there aren't yet good documentation resources available to combine these which is why I created this one, so other developers can follow my team's lead and make their life easier by providing good security for their webapps.</p>
-<p>The solution I present to you here has operated successfully inside production environments since 2015 and so have maintained it for almost 2 years now and so it's quite mature.  I write this description of how it works and it's intended as something you should try as well.</p>
+<p>The solution I present to you here has operated successfully inside production environments since 2015 for almost 2 years now and so it's quite mature.  I write this how-to document to explain how it works and it's intended as a guide for you to follow as well.</p>
 <p>Here are the technology stacks used within my extended framework:</p>
 <ul>
 <li>Apereo CAS -&gt; 4.2.x</li>