Mailing-List: contact commits-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@directory.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1794489 -
 /directory/site/trunk/content/fortress/testimonials.mdtext
Date: Tue, 09 May 2017 02:39:53 -0000
To: commits@directory.apache.org
From: smckinney@apache.org
Message-Id: <20170509023953.C55FC3A0A82@svn01-us-west.apache.org>
archived-at: Tue, 09 May 2017 02:39:57 -0000

Author: smckinney
Date: Tue May  9 02:39:53 2017
New Revision: 1794489

URL: http://svn.apache.org/viewvc?rev=1794489&view=rev
Log:
last

Modified:
    directory/site/trunk/content/fortress/testimonials.mdtext

Modified: directory/site/trunk/content/fortress/testimonials.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/fortress/testimonials.mdtext?rev=1794489&r1=1794488&r2=1794489&view=diff
==============================================================================
--- directory/site/trunk/content/fortress/testimonials.mdtext (original)
+++ directory/site/trunk/content/fortress/testimonials.mdtext Tue May  9 02:39:53 2017
@@ -17,7 +17,7 @@ I searched all available open source sol
 
 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.
 
-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.
+The solution I present to you here has operated successfully inside production environments since 2015 and so it's quite mature.  I write this how-to document to explain how it works.  It's intended as a guide for you to follow as well.
 
 Here are the technology stacks used within my extended framework:
 
@@ -27,7 +27,7 @@ Here are the technology stacks used with
  * Apache Ignite -> 1.7.0
  * Spring Framework -> 4.2.x-RELEASE
 
-There are two steps of development.  One to handle the server side and the other for the client.  The client is shared across my dev team for managing security within their web applications.
+There are two areas of development focus.  One to handle the server side and the other for the client.  The client is shared with my dev team for managing security within their web applications.
 
  1. CAS Server side development: Includes creating own implementation for AbstractUsernamePasswordAuthenticationHandler and implemening an Apache Ignite Service Registry for CAS
  2. CAS Client side development: Includes create own implementation for WebExpressionVoter and CasAuthenticationProvider