Author: buildbot
Date: Wed Jun 6 20:48:20 2012
New Revision: 820545
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/main.pageCache
websites/production/cxf/content/fediz-idp.html
websites/production/cxf/content/fediz-tomcat.html
websites/production/cxf/content/fediz.html
Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/fediz-idp.html
==============================================================================
--- websites/production/cxf/content/fediz-idp.html (original)
+++ websites/production/cxf/content/fediz-idp.html Wed Jun 6 20:48:20 2012
@@ -138,7 +138,7 @@ Apache CXF -- Fediz IDP
<div class="wiki-content">
<div id="ConfluenceContent"><h1><a shape="rect"
name="FedizIDP-FedizIDP"></a>Fediz IDP</h1>
-<p>The Fediz Identity Provider (IDP) consists of two WAR files. One is the
Security Token Service (STS) component which is responsible for validating
credentials, getting the requested claims data and issuing a SAML token. There
is no easy way for Web browsers to issue SOAP requests to the STS directly,
necessitating the second component, an IDP WAR which allows browser-based
applications to interact with the STS. The communication between the browser
and the IDP must be performed within the confines of the base HTTP 1.1
functionality and conform as closely as possible to the WS-Trust protocols
semantic.</p>
+<p>The Fediz Identity Provider (IDP) consists of two WAR files. One is the
Security Token Service (STS) component, fedizidpsts.war, which is responsible
for validating credentials, getting the requested claims data and issuing a
SAML token. There is no easy way for Web browsers to issue SOAP requests to the
STS directly, necessitating the second component, an IDP WAR (fedizidp.war)
which allows browser-based applications to interact with the STS. The
communication between the browser and the IDP must be performed within the
confines of the base HTTP 1.1 functionality and conform as closely as possible
to the WS-Trust protocols semantic.</p>
<p>The Fediz STS is based on a customized CXF STS configured to support
standard Federation use cases demonstrated by the examples.</p>
Modified: websites/production/cxf/content/fediz-tomcat.html
==============================================================================
--- websites/production/cxf/content/fediz-tomcat.html (original)
+++ websites/production/cxf/content/fediz-tomcat.html Wed Jun 6 20:48:20 2012
@@ -178,7 +178,7 @@ add the previously created directory to
-<h5><a shape="rect" name="FedizTomcat-Fedizconfiguration"></a>Fediz
configuration</h5>
+<h5><a shape="rect"
name="FedizTomcat-FedizPluginconfigurationforYourWebApplication"></a>Fediz
Plugin configuration for Your Web Application</h5>
<p>The Fediz related configuration is done in a Servlet Container independent
configuration file which is described <a shape="rect"
href="fediz-configuration.html" title="Fediz Configuration">here</a>.</p>
Modified: websites/production/cxf/content/fediz.html
==============================================================================
--- websites/production/cxf/content/fediz.html (original)
+++ websites/production/cxf/content/fediz.html Wed Jun 6 20:48:20 2012
@@ -183,7 +183,7 @@ The RP is a web application that needs t
<h2><a shape="rect" name="Fediz-Distribution"></a>Distribution</h2>
-<p>tbd</p>
+<p>For the moment, you'll need to check out the Fediz source and build them
following the instructions in "Building" below. Once built, the deployable
WARs will be located in the fediz-idp and fediz-idp-sts "target" folders
(fedizidp.war and fedizidpsts.war).</p>
<h2><a shape="rect" name="Fediz-Samples"></a>Samples</h2>
