Return-Path: X-Original-To: apmail-cxf-commits-archive@www.apache.org Delivered-To: apmail-cxf-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E92869515 for ; Wed, 6 Jun 2012 20:48:44 +0000 (UTC) Received: (qmail 59830 invoked by uid 500); 6 Jun 2012 20:48:44 -0000 Delivered-To: apmail-cxf-commits-archive@cxf.apache.org Received: (qmail 59768 invoked by uid 500); 6 Jun 2012 20:48:44 -0000 Mailing-List: contact commits-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list commits@cxf.apache.org Received: (qmail 59761 invoked by uid 99); 6 Jun 2012 20:48:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2012 20:48:44 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2012 20:48:41 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id B6B0223889E0 for ; Wed, 6 Jun 2012 20:48:20 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r820545 - in /websites/production/cxf/content: cache/main.pageCache fediz-idp.html fediz-tomcat.html fediz.html Date: Wed, 06 Jun 2012 20:48:20 -0000 To: commits@cxf.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120606204820.B6B0223889E0@eris.apache.org> 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

Fediz IDP

-

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.

+

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.

The Fediz STS is based on a customized CXF STS configured to support standard Federation use cases demonstrated by the examples.

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 -
Fediz configuration
+
Fediz Plugin configuration for Your Web Application

The Fediz related configuration is done in a Servlet Container independent configuration file which is described here.

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

Distribution

-

tbd

+

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).

Samples