Author: chris.laprun(a)jboss.com Date: 2007-06-28 23:43:05 -0400 (Thu, 28 Jun 2007) New Revision: 7634 Modified: docs/trunk/referenceGuide/en/modules/security.xml Log: - Removed empty sect2. - Fixed error on emphasis. Modified: docs/trunk/referenceGuide/en/modules/security.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/security.xml 2007-06-29 02:33:36 UTC (rev 7633) +++ docs/trunk/referenceGuide/en/modules/security.xml 2007-06-29 03:43:05 UTC (rev 7634) @@ -336,7 +336,7 @@ about it.</listitem> <listitem><emphasis>/auth/*</emphasis> : the authenticated access, requires the user to be authenticated to be used.</listitem> - <listitem>/authsec/*<emphasis></emphasis> : combine thet two previous options into a single one.</listitem> + <listitem><emphasis>/authsec/*</emphasis> : combine thet two previous options into a single one.</listitem> </itemizedlist> Usually ones should not care much about those mappings as the portal will by itself switch to the most appropriate mapping. </para> @@ -388,8 +388,6 @@ </para> </sect2> <sect2> - </sect2> - <sect2> <title>Making a programmatic security check</title> <para>Making a security check is an easy thing as it consists in created a permission of the appropriate type and make a check against the <emphasis>org.jboss.portal.spi.auth.PortalAuthorizationManager</emphasis> service. That