directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From smckin...@apache.org
Subject directory-fortress-realm git commit: FC-56 - minor realm how-to cleanup
Date Mon, 09 Feb 2015 16:54:41 GMT
Repository: directory-fortress-realm
Updated Branches:
  refs/heads/master 20f332bf3 -> 291da91c2


FC-56 - minor realm how-to cleanup


Project: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/repo
Commit: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/commit/291da91c
Tree: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/tree/291da91c
Diff: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/diff/291da91c

Branch: refs/heads/master
Commit: 291da91c244d86ec479126226c558a734d9bbe5e
Parents: 20f332b
Author: Shawn McKinney <smckinney@apache.org>
Authored: Mon Feb 9 10:54:29 2015 -0600
Committer: Shawn McKinney <smckinney@apache.org>
Committed: Mon Feb 9 10:54:29 2015 -0600

----------------------------------------------------------------------
 REALM-CONTEXT-SETUP.txt | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/blob/291da91c/REALM-CONTEXT-SETUP.txt
----------------------------------------------------------------------
diff --git a/REALM-CONTEXT-SETUP.txt b/REALM-CONTEXT-SETUP.txt
index ec09488..2cbda09 100644
--- a/REALM-CONTEXT-SETUP.txt
+++ b/REALM-CONTEXT-SETUP.txt
@@ -78,11 +78,11 @@ b. Add the following:
            containerType="TomcatContext"
            realmClasspath=""
             />
-
-    </Context>
+</Context>
 
 c. Add security constraints to target web.xml:
 
+        ...
         <security-constraint>
             <display-name>Commander Security Constraint</display-name>
             <web-resource-collection>
@@ -110,17 +110,17 @@ c. Add security constraints to target web.xml:
     </security-role>
     ...
 
-Note:  Fortress Realm is compliant with Java EE security semantics.  The above is a one simple
example.
-For more info:
+Note:  Fortress Realm follows standard Java EE security semantics.  The above is a very simple
example.
+For more info on how Java EE security is used:
 http://docs.oracle.com/javaee/6/tutorial/doc/bnbwj.html
 
-d. Redeploy web application.
+d. Redeploy web application to Tomcat.
 
-e. Login to the app.  Users that successfully authenticate and have activated at least one
role listed in auth-constraints gain access to app resources matching the url-pattern.
+e. Login to the web application.  Users that successfully authenticate and have activated
role(s) listed in auth-constraints have access to all resources matching the url-pattern(s).
 
-f. View the server logs to ensure there are no errors.
+f. View the Tomcat server logs to ensure there are no errors.
 
-g. verify that fortress realm is operating properly by viewing the following in catalina.log:
+g. Verify that fortress realm is operating properly by viewing the following in catalina.log:
 
 org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization
successful
 _________________________________________________________________________________


Mime
View raw message