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 CA5D910778 for ; Sat, 31 Aug 2013 21:19:34 +0000 (UTC) Received: (qmail 13921 invoked by uid 500); 31 Aug 2013 21:19:34 -0000 Delivered-To: apmail-cxf-commits-archive@cxf.apache.org Received: (qmail 13874 invoked by uid 500); 31 Aug 2013 21:19:34 -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 13867 invoked by uid 99); 31 Aug 2013 21:19:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 Aug 2013 21:19:34 +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; Sat, 31 Aug 2013 21:19:33 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 7E6F02388900; Sat, 31 Aug 2013 21:19:13 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1519226 - in /cxf/fediz/trunk/examples: springPreauthWebapp/README.txt wsclientWebapp/README.txt Date: Sat, 31 Aug 2013 21:19:13 -0000 To: commits@cxf.apache.org From: owulff@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20130831211913.7E6F02388900@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: owulff Date: Sat Aug 31 21:19:13 2013 New Revision: 1519226 URL: http://svn.apache.org/r1519226 Log: readme updated Modified: cxf/fediz/trunk/examples/springPreauthWebapp/README.txt cxf/fediz/trunk/examples/wsclientWebapp/README.txt Modified: cxf/fediz/trunk/examples/springPreauthWebapp/README.txt URL: http://svn.apache.org/viewvc/cxf/fediz/trunk/examples/springPreauthWebapp/README.txt?rev=1519226&r1=1519225&r2=1519226&view=diff ============================================================================== --- cxf/fediz/trunk/examples/springPreauthWebapp/README.txt (original) +++ cxf/fediz/trunk/examples/springPreauthWebapp/README.txt Sat Aug 31 21:19:13 2013 @@ -6,6 +6,10 @@ web application where WS-Federation base Fediz initializes the Spring Security Context which provides a richer security API and configuration than the Java Servlet API. +This example still requires the fediz plugin be configured on the container level +whereas the demo 'springWebapp' can be deployed into any application server as +fediz is integrated into spring security natively. + The Spring Security reference documentation provides more background information about Pre-Authentication support in Spring Security: http://static.springsource.org/spring-security/site/docs/3.2.x/reference/springsecurity-single.html#preauth Modified: cxf/fediz/trunk/examples/wsclientWebapp/README.txt URL: http://svn.apache.org/viewvc/cxf/fediz/trunk/examples/wsclientWebapp/README.txt?rev=1519226&r1=1519225&r2=1519226&view=diff ============================================================================== --- cxf/fediz/trunk/examples/wsclientWebapp/README.txt (original) +++ cxf/fediz/trunk/examples/wsclientWebapp/README.txt Sat Aug 31 21:19:13 2013 @@ -1,7 +1,11 @@ Web Service Client Web Application Demo ======================================= -This demo builds on the simpleWebapp sample to show a Relying Party (RP) web application using an IDP-provided SAML token to access a third-party web service. Here the IDP authenticates the browser user that the web application requested the token on behalf of, and uses its STS to issue the token which fulfills the web service's security requirements. From the SAML token the Web Service is informed which browser user triggered the Web Service call. +This demo builds on the simpleWebapp sample to show a Relying Party (RP) web application +using an IDP-provided SAML token to access a third-party web service. +Here the IDP authenticates the browser user that the web application requested the token on behalf of, +and uses its STS to issue the token which fulfills the web service's security requirements. +From the SAML token the Web Service is informed which browser user triggered the Web Service call. Running this sample consists of four steps: