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 2023/06/24 01:55:45 UTC

[directory-fortress-realm] branch master updated: formatting, cleanup

This is an automated email from the ASF dual-hosted git repository.

smckinney pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/directory-fortress-realm.git


The following commit(s) were added to refs/heads/master by this push:
     new 4b629a6  formatting, cleanup
4b629a6 is described below

commit 4b629a641c455d40792f67f38458f5d98f178b37
Author: Shawn McKinney <sm...@symas.com>
AuthorDate: Fri Jun 23 20:55:38 2023 -0500

    formatting, cleanup
---
 README.md              |  30 ++---
 REALM-CONTEXT-SETUP.md | 208 ++++++++++++++---------------
 REALM-HOST-SETUP.md    | 346 ++++++++++++++++++++++++-------------------------
 3 files changed, 291 insertions(+), 293 deletions(-)

diff --git a/README.md b/README.md
index 8cff792..7788711 100644
--- a/README.md
+++ b/README.md
@@ -64,30 +64,30 @@ Minimum software requirements (to build):
 1. Download the source.
 
  a. from git:
- ```
- git clone --branch 3.0.0 https://gitbox.apache.org/repos/asf/directory-fortress-realm.git
- cd directory-fortress-realm
- ```
+```
+git clone --branch 3.0.0 https://gitbox.apache.org/repos/asf/directory-fortress-realm.git
+cd directory-fortress-realm
+```
 
  b. or download package:
 
- ```
- wget http://www.apache.org/dist/directory/fortress/dist/2.0.8/fortress-realm-3.0.0-source-release.zip
- unzip fortress-realm-3.0.0-source-release.zip
- cd fortress-realm-3.0.0
- ```
+```
+wget http://www.apache.org/dist/directory/fortress/dist/[version]/fortress-realm-3.0.0-source-release.zip
+unzip fortress-realm-[version]-source-release.zip
+cd fortress-realm-[version]
+```
 
 2. Build the source
 
- ```
- mvn clean install
- ```
+```
+mvn clean install
+```
 
 3. Now build the javadoc:
 
- ```
- mvn javadoc:javadoc
- ```
+```
+mvn javadoc:javadoc
+```
 
 4. View the generated document here: [./target/site/apidocs/overview-summary.html](./target/site/apidocs/overview-summary.html).
 
diff --git a/REALM-CONTEXT-SETUP.md b/REALM-CONTEXT-SETUP.md
index b1e4853..69005c9 100644
--- a/REALM-CONTEXT-SETUP.md
+++ b/REALM-CONTEXT-SETUP.md
@@ -64,9 +64,9 @@ Everything else covered in steps that follow.  Tested on Debian, Centos & Window
 
 1. copy **FORTRESS_REALM_HOME** proxy jar to **TOMCAT_HOME**/lib/
 
- ```
- cp $FORTRESS_REALM_HOME/proxy/target/fortress-realm-proxy-[version].jar $TOMCAT_HOME/lib
- ```
+```
+cp $FORTRESS_REALM_HOME/proxy/target/fortress-realm-proxy-[version].jar $TOMCAT_HOME/lib
+```
 
 2. Restart Tomcat server for changes to take effect.
 
@@ -74,20 +74,20 @@ Everything else covered in steps that follow.  Tested on Debian, Centos & Window
 ## SECTION 3. Enable Web App to use the Context Realm
 
 1. Add a **context.xml** file to the **META-INF** folder of target web app.
- ```
- vi $MY_APP_HOME/src/main/resources/META-INF/conf/context.xml
- ```
+```
+vi $MY_APP_HOME/src/main/resources/META-INF/conf/context.xml
+```
 
 2. Add to the file:
 
- ```
- <Context reloadable="true">
-    <Realm className="org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy"
-           defaultRoles=""
-           containerType="TomcatContext"
-           contextId="HOME"
-           realmClasspath=""
-            />
+```xml
+<Context reloadable="true">
+   <Realm className="org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy"
+          defaultRoles=""
+          containerType="TomcatContext"
+          contextId="HOME"
+          realmClasspath=""
+           />
 </Context>
 ```
 
@@ -97,117 +97,117 @@ Everything else covered in steps that follow.  Tested on Debian, Centos & Window
 - realmClasspath should always be empty, for realm context setups. It will use the web app's classpath.
 
 3. Edit the web app's deployment descriptor:
- ```
- vi $MY_APP_HOME/src/main/webapp/WEB-INF/web.xml
- ```
+```
+vi $MY_APP_HOME/src/main/webapp/WEB-INF/web.xml
+```
 
 4. Add Java EE security constraint declarations to the file:
- ```
-  ...
-  <security-constraint>
-      <display-name>Commander Security Constraint</display-name>
-      <web-resource-collection>
-          <web-resource-name>Protected Area</web-resource-name>
-          <!-- Define the context-relative URL(s) to be protected -->
-          <url-pattern>/*</url-pattern>
-      </web-resource-collection>
-      <auth-constraint>
-          <!-- Anyone with one of the listed roles may access this area -->
-          <role-name>MY_ROLE_NAME</role-name>
-          ...
-      </auth-constraint>
-  </security-constraint>
-
-  <!-- Example of HTTP Basic Authentication Setup. -->
-  <login-config>
-      <auth-method>BASIC</auth-method>
-      <realm-name>FortressSecurityRealm</realm-name>
-  </login-config>
-
-  <!-- Security roles referenced by this web application -->
-  <security-role>
-      <role-name>A_ROLE_NAME_1</role-name>
-  </security-role>
-  <security-role>
-      <role-name>A_ROLE_NAME_2</role-name>
-  </security-role>
-  <security-role>
-      <role-name>A_ROLE_NAME_3</role-name>
-  </security-role>
-  ...
- ```
+```xml
+...
+<security-constraint>
+  <display-name>Commander Security Constraint</display-name>
+    <web-resource-collection>
+        <web-resource-name>Protected Area</web-resource-name>
+        <!-- Define the context-relative URL(s) to be protected -->
+        <url-pattern>/*</url-pattern>
+    </web-resource-collection>
+    <auth-constraint>
+        <!-- Anyone with one of the listed roles may access this area -->
+        <role-name>MY_ROLE_NAME</role-name>
+        ...
+    </auth-constraint>
+</security-constraint>
+
+<!-- Example of HTTP Basic Authentication Setup. -->
+<login-config>
+    <auth-method>BASIC</auth-method>
+    <realm-name>FortressSecurityRealm</realm-name>
+</login-config>
+
+<!-- Security roles referenced by this web application -->
+<security-role>
+    <role-name>A_ROLE_NAME_1</role-name>
+</security-role>
+<security-role>
+    <role-name>A_ROLE_NAME_2</role-name>
+</security-role>
+<security-role>
+    <role-name>A_ROLE_NAME_3</role-name>
+</security-role>
+...
+```
 
  *Fortress Realm follows standard Java EE security semantics.*
 
 5. Add this dependency to the Web app's **pom.xml** file.
 
- ```
- <dependency>
-     <groupId>org.apache.directory</groupId>
-     <artifactId>fortress-realm-impl</artifactId>
-     <version>${project.version}</version>
-     <classifier>classes</classifier>
-  </dependency>
-  ```
+```xml
+<dependency>
+    <groupId>org.apache.directory</groupId>
+    <artifactId>fortress-realm-impl</artifactId>
+    <version>${project.version}</version>
+    <classifier>classes</classifier>
+ </dependency>
+```
 
- *Where project.version contains target version, e.g. 1.0-RC41*
+ *Where project.version contains target version, e.g. 3.0.0*
 
 6. Add the **fortress.properties** file to the classpath of the web app.
 
  Copy the fortress.properties, created during **FORTRESS_CORE_HOME** setup, to app resource folder.
- ```
- cp $FORTRESS_CORE_HOME/config/fortress.properties $MY_APP_HOME/src/main/resources
- ```
+```
+cp $FORTRESS_CORE_HOME/config/fortress.properties $MY_APP_HOME/src/main/resources
+```
 
 7. Verify a match for target LDAP server coordinates.
- ```
- # This param tells fortress what type of ldap server in use:
- ldap.server.type=apacheds
+```properties
+# This param tells fortress what type of ldap server in use:
+ldap.server.type=apacheds
 
- # ldap host name
- host=localhost
+# ldap host name
+host=localhost
 
- # if ApacheDS is listening on
- port=10389
+# if ApacheDS is listening on
+port=10389
 
- # If ApacheDS, these credentials are used for read/write to fortress DIT
- admin.user=uid=admin,ou=system
- admin.pw=secret
+# If ApacheDS, these credentials are used for read/write to fortress DIT
+admin.user=uid=admin,ou=system
+admin.pw=secret
 
- # This is min/max settings for admin pool connections:
- min.admin.conn=1
- max.admin.conn=10
+# This is min/max settings for admin pool connections:
+min.admin.conn=1
+max.admin.conn=10
 
- # This node contains more fortress properties stored on behalf of connecting LDAP clients:
- config.realm=DEFAULT
- config.root=ou=Config,dc=example,dc=com
+# This node contains more fortress properties stored on behalf of connecting LDAP clients:
+config.realm=DEFAULT
+config.root=ou=Config,dc=example,dc=com
 
- # Used by application security components:
- perms.cached=true
+# Used by application security components:
+perms.cached=true
 
- # Fortress uses a cache:
- ehcache.config.file=ehcache.xml
+# Fortress uses a cache:
+ehcache.config.file=ehcache.xml
 
- # Default for pool reconnect flag is false:
- enable.pool.reconnect=true
- ```
+# Default for pool reconnect flag is false:
+enable.pool.reconnect=true
+```
 
 8. Add two other files, **ehcache.xml** and **log4j2.xml** to classpath of the web app.
 
- ```
- cp $FORTRESS_REALM_HOME/conf/echcache.xml $MY_APP_HOME/src/main/resources
- cp $FORTRESS_REALM_HOME/conf/log4j2.xml $MY_APP_HOME/src/main/resources
- ```
+```bash
+cp $FORTRESS_REALM_HOME/conf/echcache.xml $MY_APP_HOME/src/main/resources
+cp $FORTRESS_REALM_HOME/conf/log4j2.xml $MY_APP_HOME/src/main/resources
+```
 
 9. Verify these configuration artifacts are properly staged to your app resource folder:
- ```
- x@machine:~/MY_APP_HOME/src/main/resources$ ls -l
- ...
- -rwxrwxr-x 1 x y 5905 Jan 23 12:41 ehcache.xml
- -rw-rw-r-- 1 x y 1161 Jan 23 12:41 fortress.properties
- -rw-rw-r-- 1 x y 1235 Jan 23 12:41 log4j2.xml
- ...
- ```
+```bash
+~/MY_APP_HOME/src/main/resources$ ls -l
+...
+-rwxrwxr-x 1 x y 5905 Jan 23 12:41 ehcache.xml
+-rw-rw-r-- 1 x y 1161 Jan 23 12:41 fortress.properties
+-rw-rw-r-- 1 x y 1235 Jan 23 12:41 log4j2.xml
+...
+```
  *Fortress needs all three files in its classpath.*
 
 10. Redeploy web application to Tomcat.
@@ -216,12 +216,12 @@ Everything else covered in steps that follow.  Tested on Debian, Centos & Window
 
 12. Verify that realm is operating properly per Tomcat server log:
 
- ```
- tail -f -n10000 $TOMCAT_HOME/logs/catalina.out
- ...
- org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
- ...
- ```
+```bash
+tail -f -n10000 $TOMCAT_HOME/logs/catalina.out
+...
+org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
+...
+```
 
 Realm Usage Notes:
 * This automatically enforces authentication and coarse-gained authorization (isUserInRole) checking for a single web app.
diff --git a/REALM-HOST-SETUP.md b/REALM-HOST-SETUP.md
index a363834..a40cef3 100644
--- a/REALM-HOST-SETUP.md
+++ b/REALM-HOST-SETUP.md
@@ -20,7 +20,6 @@
  * Apache Fortress Realm Host System Architecture Diagram
  ![Apache Fortress Realm Host System Architecture](images/fortress-realm-host-system-arch.png "Apache Fortress Realm Host System Architecture")
 
-
 -------------------------------------------------------------------------------
 ## Table of Contents
 
@@ -70,59 +69,59 @@ Everything else covered in steps that follow.  Tested on Debian, Centos & Window
 
  Copy fortress-realm-proxy-[version].jar to TOMCAT_HOME/lib/ folder:
 
- ```
- cp $FORTRESS_REALM_HOME/proxy/fortress-realm-proxy-[version].jar $TOMCAT_HOME/lib
- ```
+```
+cp $FORTRESS_REALM_HOME/proxy/fortress-realm-proxy-[version].jar $TOMCAT_HOME/lib
+```
 
 2. Configure the Fortress Realm for target LDAP server usage.
 
  Copy the **fortress.properties**, created during **FORTRESS_CORE_HOME** setup, to this package's conf folder.
- ```
- cp $FORTRESS_CORE_HOME/config/fortress.properties $FORTRESS_REALM_HOME/conf
- ```
+```
+cp $FORTRESS_CORE_HOME/config/fortress.properties $FORTRESS_REALM_HOME/conf
+```
 
 3. Verify a match for target LDAP server coordinates.
- ```
- # This param tells fortress what type of ldap server in use:
- ldap.server.type=apacheds
+```properties
+# This param tells fortress what type of ldap server in use:
+ldap.server.type=apacheds
 
- # ldap host name
- host=localhost
+# ldap host name
+host=localhost
 
- # if ApacheDS is listening on
- port=10389
+# if ApacheDS is listening on
+port=10389
 
- # If ApacheDS, these credentials are used for read/write to fortress DIT
- admin.user=uid=admin,ou=system
- admin.pw=secret
+# If ApacheDS, these credentials are used for read/write to fortress DIT
+admin.user=uid=admin,ou=system
+admin.pw=secret
 
- # This is min/max settings for admin pool connections:
- min.admin.conn=1
- max.admin.conn=10
+# This is min/max settings for admin pool connections:
+min.admin.conn=1
+max.admin.conn=10
 
- # This node contains more fortress properties stored on behalf of connecting LDAP clients:
- config.realm=DEFAULT
- config.root=ou=Config,dc=example,dc=com
+# This node contains more fortress properties stored on behalf of connecting LDAP clients:
+config.realm=DEFAULT
+config.root=ou=Config,dc=example,dc=com
 
- # Used by application security components:
- perms.cached=true
+# Used by application security components:
+perms.cached=true
 
- # Fortress uses a cache:
- ehcache.config.file=ehcache.xml
+# Fortress uses a cache:
+ehcache.config.file=ehcache.xml
 
- # Default for pool reconnect flag is false:
- enable.pool.reconnect=true
- ```
+# Default for pool reconnect flag is false:
+enable.pool.reconnect=true
+```
 
 4. Verify the configuration artifacts are present.
- ```
- x@machine:~/FORTRESS_REALM_HOME/conf$ ls -l
- ...
- -rwxrwxr-x 1 x y 5905 Jan 23 12:41 ehcache.xml
- -rw-rw-r-- 1 x y 1161 Jan 23 12:41 fortress.properties
- -rw-rw-r-- 1 x y 1235 Jan 23 12:41 log4j2.xml
- ...
- ```
+```bash
+~/FORTRESS_REALM_HOME/conf$ ls -l
+...
+-rwxrwxr-x 1 x y 5905 Jan 23 12:41 ehcache.xml
+-rw-rw-r-- 1 x y 1161 Jan 23 12:41 fortress.properties
+-rw-rw-r-- 1 x y 1235 Jan 23 12:41 log4j2.xml
+...
+```
 
  *Fortress needs all three files.*
 
@@ -130,31 +129,31 @@ ________________________________________________________________________________
 ## SECTION 3. Enable Tomcat Global Security
 
 1. Edit **TOMCAT_HOME**/conf/server.xml:
- ```
- vi $TOMCAT_HOME/conf/server.xml
- ```
+```bash
+vi $TOMCAT_HOME/conf/server.xml
+```
 
 2. Comment out entry to UserDatabase:
- ```
- <!--Resource name="UserDatabase" auth="Container"
-    type="org.apache.catalina.UserDatabase"
-    description="User database that can be updated and saved"
-    factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
-    pathname="conf/tomcat-users.xml" /-->
- ```
+```xml
+<!--Resource name="UserDatabase" auth="Container"
+   type="org.apache.catalina.UserDatabase"
+   description="User database that can be updated and saved"
+   factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
+   pathname="conf/tomcat-users.xml" /-->
+```
 
 3. Enable Tomcat global security to use the Fortress Realm.
  Add the following to the same file:
- ```
- <Realm className="org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy"
-     debug="0"
-     resourceName="UserDatabase"
-	 containerType="Tomcat7"
-     realmClasspath="$FORTRESS_REALM_HOME/conf:$FORTRESS_REALM_HOME/impl/target/fortress-realm-impl-uber-[version].jar"
-     defaultRoles=""
-     contextId="HOME"
-	/>
- ```
+```xml
+<Realm className="org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy"
+   debug="0"
+   resourceName="UserDatabase"
+   containerType="Tomcat7"
+   realmClasspath="$FORTRESS_REALM_HOME/conf:$FORTRESS_REALM_HOME/impl/target/fortress-realm-impl-uber-[version].jar"
+   defaultRoles=""
+   contextId="HOME"
+/>
+```
 
  *Here the FORTRESS_REALM_HOME conf folder and implementation jar are being declared to Tomcat server.  Ensure that you stage these files outside of TOMCAT_HOME to ensure remaining clear of Tomcat's system classpath.*
 
@@ -164,50 +163,50 @@ ________________________________________________________________________________
 
 6. Verify it worked:
 
- ```
- tail -f -n10000 $TOMCAT_HOME/logs/catalina.out
- ...
- org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
- ...
- ```
+```bash
+tail -f -n10000 $TOMCAT_HOME/logs/catalina.out
+...
+org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
+...
+```
 
 _________________________________________________________________________________
 ## SECTION 4. Enable Web App to use the Global Realm
 
 1. Edit the web app's deployment descriptor:
- ```
- vi $MY_APP_HOME/src/main/webapp/WEB-INF/web.xml
- ```
+```
+vi $MY_APP_HOME/src/main/webapp/WEB-INF/web.xml
+```
 
 2. Add security constraints to the file:
- ```
-  ...
-  <security-constraint>
-      <display-name>Commander Security Constraint</display-name>
-      <web-resource-collection>
-          <web-resource-name>Protected Area</web-resource-name>
-          <!-- Define the context-relative URL(s) to be protected -->
-          <url-pattern>/*</url-pattern>
-      </web-resource-collection>
-      <auth-constraint>
-          <!-- Anyone with one of the listed roles may access this area -->
-          <role-name>MY_ROLE_NAME</role-name>
-          ...
-      </auth-constraint>
-  </security-constraint>
-
-  <!-- Example of HTTP Basic Authentication Setup. -->
-  <login-config>
-      <auth-method>BASIC</auth-method>
-      <realm-name>FortressSecurityRealm</realm-name>
-  </login-config>
-
-  <!-- Security roles referenced by this web application -->
-  <security-role>
-      <role-name>MY_ROLE_NAME</role-name>
-  </security-role>
-  ...
- ```
+```xml
+...
+<security-constraint>
+    <display-name>Commander Security Constraint</display-name>
+    <web-resource-collection>
+        <web-resource-name>Protected Area</web-resource-name>
+        <!-- Define the context-relative URL(s) to be protected -->
+        <url-pattern>/*</url-pattern>
+    </web-resource-collection>
+    <auth-constraint>
+        <!-- Anyone with one of the listed roles may access this area -->
+        <role-name>MY_ROLE_NAME</role-name>
+        ...
+    </auth-constraint>
+</security-constraint>
+
+<!-- Example of HTTP Basic Authentication Setup. -->
+<login-config>
+    <auth-method>BASIC</auth-method>
+    <realm-name>FortressSecurityRealm</realm-name>
+</login-config>
+
+<!-- Security roles referenced by this web application -->
+<security-role>
+    <role-name>MY_ROLE_NAME</role-name>
+</security-role>
+...
+```
 
  *Fortress Realm follows standard Java EE security semantics.*
 
@@ -217,12 +216,12 @@ ________________________________________________________________________________
 
 5. Verify that the fortress realm is operating properly by viewing the Tomcat server log:
 
- ```
- tail -f -n10000 $TOMCAT_HOME/logs/catalina.out
- ...
- org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
- ...
- ```
+```bash
+tail -f -n10000 $TOMCAT_HOME/logs/catalina.out
+...
+org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7 policy agent initialization successful
+...
+```
 
 Realm Usage Notes:
 * Global security is now enabled under Tomcat.
@@ -238,14 +237,13 @@ This section provides instructions for using the Tomcat Manager application to t
 
 2. Verify/enable role name. Edit **TOMCAT_HOME**/webapps/manager/WEB-INF/web.xml
 
- ```
- <!-- Security roles referenced by this web application --/>
- <security-role/>
-     <description/>
-     The role that is required to log in to the Manager Application
-     </description/>
-     <role-name/>manager</role-name/>
- </security-role/>
+```xml
+<security-role/>
+    <description/>
+    The role that is required to log in to the Manager Application
+    </description/>
+    <role-name/>manager</role-name/>
+</security-role/>
  ```
 
 3. Add and assign that role to a user.
@@ -263,64 +261,64 @@ ________________________________________________________________________________
 
 1. Server can't find config files (realmClasspath=**FORTRESS_REALM_HOME**/conf")
 
- ```
- Jul 15, 2011 8:21:16 PM us.jts.sentry.tomcat.Tc7AccessMgrProxy initialize
- INFO: us.jts.sentry.tomcat.Tc7AccessMgrProxy.initialize - instantiate policy agent name: us.jts.sentry.tomcat.TcAccessMgrImpl
- 2011-07-15 20:21:17,053 (FATAL) us.jts.configuration.Config static init: Error, null configuration file: fortress.properties
- Jul 15, 2011 8:21:17 PM us.jts.sentry.tomcat.Tc7AccessMgrProxy startInternal
- SEVERE: us.jts.sentry.tomcat.Tc7AccessMgrProxy.startInternal caught Throwable=java.lang.ExceptionInInitializerError
- java.lang.ExceptionInInitializerError
-        at us.jts.sentry.J2eePolicyMgrFactory.<clinit>(J2eePolicyMgrFactory.java:32)
-        at us.jts.sentry.tomcat.TcAccessMgrImpl.<init>(TcAccessMgrImpl.java:35)
-        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
-        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
-        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
-        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
-        at java.lang.Class.newInstance0(Class.java:355)
-        at java.lang.Class.newInstance(Class.java:308)
-        at us.jts.sentry.tomcat.Tc7AccessMgrProxy.initialize(Tc7AccessMgrProxy.java:112)
-        at us.jts.sentry.tomcat.Tc7AccessMgrProxy.startInternal(Tc7AccessMgrProxy.java:236)
-        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
-        at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1026)
-        at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:291)
-        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
-        at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
-        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
-        at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:727)
-        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
-        at org.apache.catalina.startup.Catalina.start(Catalina.java:620)
-        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
-        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
-        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
-        at java.lang.reflect.Method.invoke(Method.java:597)
-        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:303)
-        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:431)
- Caused by: java.lang.RuntimeException: us.jts.configuration.Config static init: Error, null configuration file: fortress.properties
-        at us.jts.configuration.Config.<clinit>(Config.java:51)
-        ... 25 more
- ```
+```bash
+Jul 15, 2011 8:21:16 PM us.jts.sentry.tomcat.Tc7AccessMgrProxy initialize
+INFO: us.jts.sentry.tomcat.Tc7AccessMgrProxy.initialize - instantiate policy agent name: us.jts.sentry.tomcat.TcAccessMgrImpl
+2011-07-15 20:21:17,053 (FATAL) us.jts.configuration.Config static init: Error, null configuration file: fortress.properties
+Jul 15, 2011 8:21:17 PM us.jts.sentry.tomcat.Tc7AccessMgrProxy startInternal
+SEVERE: us.jts.sentry.tomcat.Tc7AccessMgrProxy.startInternal caught Throwable=java.lang.ExceptionInInitializerError
+java.lang.ExceptionInInitializerError
+       at us.jts.sentry.J2eePolicyMgrFactory.<clinit>(J2eePolicyMgrFactory.java:32)
+       at us.jts.sentry.tomcat.TcAccessMgrImpl.<init>(TcAccessMgrImpl.java:35)
+       at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
+       at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
+       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
+       at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
+       at java.lang.Class.newInstance0(Class.java:355)
+       at java.lang.Class.newInstance(Class.java:308)
+       at us.jts.sentry.tomcat.Tc7AccessMgrProxy.initialize(Tc7AccessMgrProxy.java:112)
+       at us.jts.sentry.tomcat.Tc7AccessMgrProxy.startInternal(Tc7AccessMgrProxy.java:236)
+       at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
+       at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1026)
+       at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:291)
+       at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
+       at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
+       at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
+       at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:727)
+       at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
+       at org.apache.catalina.startup.Catalina.start(Catalina.java:620)
+       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
+       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
+       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
+       at java.lang.reflect.Method.invoke(Method.java:597)
+       at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:303)
+       at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:431)
+Caused by: java.lang.RuntimeException: us.jts.configuration.Config static init: Error, null configuration file: fortress.properties
+       at us.jts.configuration.Config.<clinit>(Config.java:51)
+       ... 25 more
+```
 
  ACTION: Ensure realm classpath points to Fortress configuration folder that contains fortress.properties config file.
 
 2. Server can't find proxy jar (Realm className="org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy")
- ```
- INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path...
- Apr 22, 2011 10:24:04 PM org.apache.tomcat.util.digester.Digester startElement
- SEVERE: Begin event threw exception
- java.lang.ClassNotFoundException: org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy
- ```
+```bash
+INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path...
+Apr 22, 2011 10:24:04 PM org.apache.tomcat.util.digester.Digester startElement
+SEVERE: Begin event threw exception
+java.lang.ClassNotFoundException: org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy
+```
 
  ACTION: Ensure fortress-realm-proxy jar copied to TOMCAT_HOME/lib folder.
 
 3. Server can't find binaries (realmClasspath="**FORTRESS_REALM_HOME**/impl/target/fortress-realm-impl-uber-[version].jar")
- ```
- Apr 22, 2011 10:22:25 PM org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy initialize
- SEVERE: Fortress Tomcat Realm.initialize java.lang.ClassNotFoundException=java.lang.ClassNotFoundException: org.apache.directory.fortress.realm.tomcat.TcAccessMgrImpl
- Apr 22, 2011 10:22:25 PM org.apache.directory.fortress.realm.tomcat.TcAccessMgrProxy start
- SEVERE: Fortress Tomcat Realm.start caught Exception=java.lang.RuntimeException: Fortress Tomcat Realm.initialize java.lang.ClassNotFoundException=java.lang.ClassNotFoundException: org.apache.directory.fortress.realm.tomcat.TcAccessMgrImpl
- java.lang.RuntimeException: Fortress Tomcat Realm.initialize java.lang.ClassNotFoundException=java.lang.ClassNotFoundException: org.apache.directory.fortress.realm.tomcat.TcAccessMgrImpl
-        at org.apache.directory.fortress.realm.tomcat.TcAccessMgrProxy.initialize(TcAccessMgrProxy.java:118)
- ```
+```bash
+Apr 22, 2011 10:22:25 PM org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy initialize
+SEVERE: Fortress Tomcat Realm.initialize java.lang.ClassNotFoundException=java.lang.ClassNotFoundException: org.apache.directory.fortress.realm.tomcat.TcAccessMgrImpl
+Apr 22, 2011 10:22:25 PM org.apache.directory.fortress.realm.tomcat.TcAccessMgrProxy start
+SEVERE: Fortress Tomcat Realm.start caught Exception=java.lang.RuntimeException: Fortress Tomcat Realm.initialize java.lang.ClassNotFoundException=java.lang.ClassNotFoundException: org.apache.directory.fortress.realm.tomcat.TcAccessMgrImpl
+java.lang.RuntimeException: Fortress Tomcat Realm.initialize java.lang.ClassNotFoundException=java.lang.ClassNotFoundException: org.apache.directory.fortress.realm.tomcat.TcAccessMgrImpl
+       at org.apache.directory.fortress.realm.tomcat.TcAccessMgrProxy.initialize(TcAccessMgrProxy.java:118)
+```
 
  ACTION: Ensure realm classpath points fortress-realm-impl-uber jar, i.e. **FORTRESS_REALM_HOME**/impl/target/fortress-realm-impl-uber-[version].jar.
 
@@ -328,21 +326,21 @@ ________________________________________________________________________________
 
  The Fortress Realm requires Tomcat version's 7 and beyond.  If you are running Tomcat 4, 5 or 6 and see error that looks like this:
 
- ```
- SEVERE: An exception or error occurred in the container during the request processing
- java.lang.RuntimeException: org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxyauthenticate detected Fortress Tomcat7 Realm not initialized correctly.  Check your Fortress Realm configuration
-        at org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.authenticate(Tc7AccessMgrProxy.java:161)
-        at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:259)
-        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:449)
-        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
-        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
-        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
-        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
-        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
-        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
-        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
-        at java.lang.Thread.run(Thread.java:662)
- ```
+```bash
+SEVERE: An exception or error occurred in the container during the request processing
+java.lang.RuntimeException: org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxyauthenticate detected Fortress Tomcat7 Realm not initialized correctly.  Check your Fortress Realm configuration
+       at org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.authenticate(Tc7AccessMgrProxy.java:161)
+       at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:259)
+       at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:449)
+       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
+       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
+       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
+       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
+       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
+       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
+       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
+       at java.lang.Thread.run(Thread.java:662)
+```
 
  ACTION: Install and use Tomcat version 7 and later in your target machine.