You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by sm...@apache.org on 2015/02/10 00:36:50 UTC
directory-fortress-realm git commit: FC-56 - more realm setup doc
cleanup
Repository: directory-fortress-realm
Updated Branches:
refs/heads/master 291da91c2 -> 781c8065e
FC-56 - more realm setup doc 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/781c8065
Tree: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/tree/781c8065
Diff: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/diff/781c8065
Branch: refs/heads/master
Commit: 781c8065ea2b63817c2a5a6b55121ae51883b7fc
Parents: 291da91
Author: Shawn McKinney <sm...@apache.org>
Authored: Mon Feb 9 17:36:38 2015 -0600
Committer: Shawn McKinney <sm...@apache.org>
Committed: Mon Feb 9 17:36:38 2015 -0600
----------------------------------------------------------------------
REALM-CONTEXT-SETUP.txt | 14 ++++----------
REALM-HOST-SETUP.txt | 22 ++++++++++------------
2 files changed, 14 insertions(+), 22 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/blob/781c8065/REALM-CONTEXT-SETUP.txt
----------------------------------------------------------------------
diff --git a/REALM-CONTEXT-SETUP.txt b/REALM-CONTEXT-SETUP.txt
index 2cbda09..b4b4b0d 100644
--- a/REALM-CONTEXT-SETUP.txt
+++ b/REALM-CONTEXT-SETUP.txt
@@ -36,7 +36,7 @@ Last updated: February 9, 2015
- Restart Tomcat server after any changes to Tomcat config, Fortress config or lib files.
-- Common misconfiguration issues related to Fortress, LDAP and Tomcat are located in section III.
+- Common misconfiguration issues related to Fortress, LDAP and Tomcat are located at the end of REALM-HOST-SETUP.txt.
___________________________________________________________________________________
###################################################################################
# SECTION 0. Prerequisites for Fortress Realm installation and usage with Tomcat
@@ -52,13 +52,13 @@ ________________________________________________________________________________
###################################################################################
# SECTION 1: Prepare Machine
###################################################################################
-a. Follow instructions in README.txt to build and install fortress realm.
+a. Follow instructions in README.txt to build and install fortress realm component.
b. copy fortress-realm-proxy-[version].jar to TOMCAT_HOME/lib/
# cp [directory-fortress-realm]/proxy/fortress-realm-proxy-[version].jar TOMCAT_HOME/lib
-Where [directory-fortress-core] is base folder of the fortress core source package.
+Where [directory-fortress-realm] is base folder of this source package.
c. Restart tomcat server instance for changes to take effect.
_________________________________________________________________________________
@@ -122,10 +122,4 @@ 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:
-org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
-_________________________________________________________________________________
-###################################################################################
-# Common troubleshooting tips:
-###################################################################################
-
-Found inside REALM-HOST-SETUP.txt
\ No newline at end of file
+org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/blob/781c8065/REALM-HOST-SETUP.txt
----------------------------------------------------------------------
diff --git a/REALM-HOST-SETUP.txt b/REALM-HOST-SETUP.txt
index face84a..b2c3872 100644
--- a/REALM-HOST-SETUP.txt
+++ b/REALM-HOST-SETUP.txt
@@ -18,25 +18,23 @@
#
___________________________________________________________________________________
###################################################################################
-INSTRUCTIONS TO ENABLE FORTRESS REALM for ALL Web Applications under Tomcat
+INSTRUCTIONS TO ENABLE FORTRESS REALM for Tomcat Host
Last updated: February 9, 2015
-----------------------------------------------------------------------------------
###################################################################################
# Guidelines & Tips
###################################################################################
-- This document describes how to enable Fortress Realm to provide security for
- Tomcat server virtual host. Follow these steps and this component will be default security
- provider for all applications within a particular Tomcat server instance.
+- This document describes how to enable Fortress Realm to provide security for all apps running
+ inside a Tomcat server virtual host.
-- It is not necessary to enable Fortress Realm in this way to enable web app to use Java EE security.
- If you want to target a single web application, and not enable for entire host, follow the Tomcat instructions in the 'REALM-CONTEXT-SETUP.txt'
+- To target a single web application, and not enable for entire host, follow the Tomcat instructions in the 'REALM-CONTEXT-SETUP.txt'
- In the document that follows, replace "[version]" with Fortress Realm version label.
For example - if Fortress Realm 1.0 release, change fortress-realm-proxy-[version].jar to fortress-realm-proxy-1.0.jar
- Restart Tomcat server after any changes to Tomcat config, Fortress config or lib files.
-- Common misconfiguration issues related to Fortress, LDAP and Tomcat are located in section III.
+- Common misconfiguration issues related to Fortress, LDAP and Tomcat are located at the end of this document.
___________________________________________________________________________________
###################################################################################
# SECTION 0. Prerequisites for Fortress Realm installation and usage with Tomcat
@@ -52,13 +50,13 @@ ________________________________________________________________________________
###################################################################################
# SECTION 1: Prepare Machine
###################################################################################
-a. Follow instructions in README.txt to build and install fortress realm.
+a. Follow instructions in README.txt to build and install fortress realm component.
b. copy fortress-realm-proxy-[version].jar to TOMCAT_HOME/lib/
# cp [directory-fortress-realm]/proxy/fortress-realm-proxy-[version].jar TOMCAT_HOME/lib
-Where [directory-fortress-core] is base folder of the fortress core source package.
+Where [directory-fortress-realm] is base folder of this source package.
c. Configure Fortress Realm for target LDAP server
@@ -103,11 +101,10 @@ f. verify that fortress realm started successfully by viewing following message
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
_________________________________________________________________________________
###################################################################################
-# SECTION 3: Test with Tomcat Manager App
+# SECTION 3: Test with Tomcat Manager App (Optional)
###################################################################################
Note: this section provides instructions for using the Tomcat Manager application to test Fortress Realm.
-This is not necessary if you have your own Java EE security enabled web application to test with.
a. Enable Tomcat Manager application. note: check the Tomcat documentation on how to do this.
@@ -121,7 +118,8 @@ b. Verify/enable role name. Edit TOMCAT_HOME/webapps/manager/WEB-INF/web.xml
<role-name/>manager</role-name/>
</security-role/>
-c. run fortress-core load file TomcatManagerUser.xml
+c. Run TomcatManagerUser.xml located in [directory-fortress-core]/ldap/setup/ folder.
+ See 'SECTION 10. Instructions to load policy data using maven fortress-load.' from directory-fortress-core README.txt.
d. Test logon onto the Tomcat Manager app.