svn commit: r817625 - in /websites/production/cxf/content: cache/main.pageCache fediz.html tomcat.html

[bu...@apache.org]

Author: buildbot
Date: Mon May 14 19:48:06 2012
New Revision: 817625

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/fediz.html
    websites/production/cxf/content/tomcat.html

Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/fediz.html
==============================================================================
--- websites/production/cxf/content/fediz.html (original)
+++ websites/production/cxf/content/fediz.html Mon May 14 19:48:06 2012
@@ -171,16 +171,16 @@ The RP is the web application which shou
 
 <p>It's recommended to deploy the IDP and the web application (RP) into different container instances as in a production deployment. The container with the IDP can be used during development and testing for any web application.</p>
 
-<h5><a shape="rect" name="Fediz-SettinguptheIDP"></a>Setting up the IDP</h5>
+<h3><a shape="rect" name="Fediz-SettinguptheIDP"></a>Setting up the IDP</h3>
 
 <p>The following blog entries describe how to set up the IDP:</p>
 
 <p><a shape="rect" class="external-link" href="http://owulff.blogspot.com/2011/10/configure-and-deploy-cxf-25-sts-part-i.html" rel="nofollow">STS WAR</a><br clear="none">
 <a shape="rect" class="external-link" href="http://owulff.blogspot.com/2011/10/configure-and-deploy-identity-provider.html" rel="nofollow">IDP WAR</a></p>
 
-<h5><a shape="rect" name="Fediz-SetuptheRelyingPartyContainer"></a>Set up the Relying Party Container</h5>
+<h3><a shape="rect" name="Fediz-SetuptheRelyingPartyContainer"></a>Set up the Relying Party Container</h3>
 
-<p>An individual plugin is deployed in each container. But most of the configuration is container independent and described <a shape="rect" href="configuration.html" title="Configuration">here</a></p>
+<p>The Fediz plugin is deployed into the Relying Party (RP) container. The security mechanism is not specified by JEE. Even it is very similar in each Servlet Container there are some differences which requires dedicated Fediz plugins for each Servlet Container implementation. Most of the configuration is container independent and described <a shape="rect" href="configuration.html" title="Configuration">here</a></p>
 
 <p>The following lists shows the supported containers and the location of the installation and configuration page.</p>
 <ul><li><a shape="rect" href="tomcat.html" title="Tomcat">Tomcat 7 </a></li></ul>

Modified: websites/production/cxf/content/tomcat.html
==============================================================================
--- websites/production/cxf/content/tomcat.html (original)
+++ websites/production/cxf/content/tomcat.html Mon May 14 19:48:06 2012
@@ -154,7 +154,9 @@ add the previously created directory to 
 
 <h3><a shape="rect" name="Tomcat-Configuration"></a>Configuration</h3>
 
-<p>The current release of the federation plugin requires to configure the FederationAuthenticator of Fediz like any other Valve in Tomcat which is described here <a shape="rect" class="external-link" href="http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html">here</a>.</p>
+<p>The Fediz related configuration is Container independent and described <a shape="rect" href="configuration.html" title="Configuration">here</a>.</p>
+
+<p>The Fediz plugin requires to configure the FederationAuthenticator like any other Valve in Tomcat which is described here <a shape="rect" class="external-link" href="http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html">here</a>.</p>
 
 <p>A valve can be configured on different levels like <em>Host</em> or <em>Context</em>. The Fediz configuration file allows to configure all servlet contexts in one file or choose one file per Servlet Context. If you choose to have one Fediz configuration file per Servlet Context then you must configure the FederationAuthenticator on the <em>Context</em> level otherwise on the <em>Host</em> level in the Tomcat configuration file <em>server.xml</em></p>