directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From smckin...@apache.org
Subject svn commit: r1794240 - /directory/site/trunk/content/fortress/testimonials.mdtext
Date Sun, 07 May 2017 18:04:19 GMT
Author: smckinney
Date: Sun May  7 18:04:19 2017
New Revision: 1794240

URL: http://svn.apache.org/viewvc?rev=1794240&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=1794240&r1=1794239&r2=1794240&view=diff
==============================================================================
--- directory/site/trunk/content/fortress/testimonials.mdtext (original)
+++ directory/site/trunk/content/fortress/testimonials.mdtext Sun May  7 18:04:19 2017
@@ -398,4 +398,4 @@ One thing that I love about CAS, even if
 
 ##Next Steps
 
- The next step should be implementing ARBAC solution. Since I donn't allow people to create
a conditional statement inside their code to check for roles, buttons or page elements that
should be not accessible for specific users will appear, even they can't perform that action.
 This causes some confusion in terms or usability for my users. With ARBAC I believe I can
do a whitelist for the page attributes and increase the usability for the user.
+ Next should be implementing ARBAC solution. Since I don't allow people to create conditional
statements inside their application code to check for roles, buttons or page elements that
should be not accessible for specific users will appear on their pages, even they can't perform
that particular action.  This causes some confusion in terms or usability for my users. With
ARBAC I believe I can do a whitelist for the page attributes and increase the usability for
the user.



Mime
View raw message