Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 29D6C102C6 for ; Wed, 28 Aug 2013 08:51:03 +0000 (UTC) Received: (qmail 11440 invoked by uid 500); 28 Aug 2013 08:51:00 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 11377 invoked by uid 500); 28 Aug 2013 08:51:00 -0000 Mailing-List: contact dev-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 dev@cxf.apache.org Received: (qmail 10407 invoked by uid 99); 28 Aug 2013 08:50:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Aug 2013 08:50:54 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [160.92.103.80] (HELO smtp1.mail.atosorigin.com) (160.92.103.80) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Aug 2013 08:50:47 +0000 Received: from localhost (localhost [127.0.0.1]) by smtp1.mail.atosorigin.com (Postfix) with ESMTP id 77FF67E00D for ; Wed, 28 Aug 2013 10:50:27 +0200 (CEST) Received: from mail.awl.fr.atosorigin.com (serv-smtp-wse01.fr.atosworldline.com [160.92.103.180]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "mail.awl.fr.atosorigin.com", Issuer "VeriSign Class 3 Secure Server CA - G3" (verified OK)) by smtp1.mail.atosorigin.com (Postfix) with ESMTPS id 739B27E00A for ; Wed, 28 Aug 2013 10:50:27 +0200 (CEST) X-ME-UUID: 20130828085027473.739B27E00A@smtp1.mail.atosorigin.com Received: from frspx302.fr01.awl.atosorigin.net (10.24.253.187) by frspx401.priv.atos.fr (10.24.220.7) with Microsoft SMTP Server (TLS) id 8.3.298.1; Wed, 28 Aug 2013 10:50:27 +0200 Received: from frvdx201.fr01.awl.atosorigin.net (10.16.253.37) by frspx302.fr01.awl.atosorigin.net (10.24.253.187) with Microsoft SMTP Server (TLS) id 8.3.298.1; Wed, 28 Aug 2013 10:50:26 +0200 Received: from FRVDX100.fr01.awl.atosorigin.net ([10.16.253.46]) by frvdx201.fr01.awl.atosorigin.net ([10.16.253.37]) with mapi; Wed, 28 Aug 2013 10:50:26 +0200 From: Beucher Thierry To: "dev@cxf.apache.org" Date: Wed, 28 Aug 2013 10:50:25 +0200 Subject: RE: Release Fediz 1.1.0... Thread-Topic: Release Fediz 1.1.0... Thread-Index: Ac6d17moTkVKdCW8SIGE7ZOkstl4WgBOmYVAAPwqVOAALzomQwAC59lw Message-ID: References: <79AB4452999C844D9920E03635332731115F8003@S10BE002.SH10.lan> , <79AB4452999C844D9920E0363533273111724842@S10BE002.SH10.lan> In-Reply-To: <79AB4452999C844D9920E0363533273111724842@S10BE002.SH10.lan> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi Oli, I am currently working on Jetty issue, I'm on the right track ... -----Message d'origine----- De : Oliver Wulff [mailto:owulff@talend.com] Envoy=E9 : mercredi 28 ao=FBt 2013 09:29 =C0 : dev@cxf.apache.org Objet : RE: Release Fediz 1.1.0... Hi Thierry I've tested the patch and it works when you deploy the IDP in Tomcat (stand= alone, systests) but the jetty systests fail. I've updated JIRA. Can you look into this? BTW, I'm working on FEDIZ-15. The Federation Metadata document should be av= ailable via the following url: https://://FederationMetadata/2007-06/FederationMetada= ta.xml What is your recommendation to plug that into spring web flow? Thanks Oli ------ Oliver Wulff Blog: http://owulff.blogspot.com Solution Architect http://coders.talend.com Talend Application Integration Division http://www.talend.com ________________________________________ From: Beucher Thierry [thierry.beucher@worldline.com] Sent: 27 August 2013 15:30 To: dev@cxf.apache.org Subject: TR: Release Fediz 1.1.0... Hi Oli, I added the patch about "wctx" to FEDIZ-3 ... Thanks _____________________________________________ De : Beucher Thierry Envoy=E9 : jeudi 22 ao=FBt 2013 10:50 =C0 : 'dev@cxf.apache.org' Objet : RE: Release Fediz 1.1.0... Hi all, I am currently checking the last trunk state, focusing myself on FEDIZ-3 fe= ature. I must also providing a short patch about two points raised by Oliver : * If I choose realm B (redirect to remote idp happens), the wctx is u= sed. The form posted to the rp contains the wctx with the same value. After= the wctx has been posted to the IDP, it must be cleared. * If you now clear the cookie with rp, you get redirected and the wct= x is still sent to the RP but empty this time. I will do everything to have it ready this weekend. Thanks -----Message d'origine----- De : Oliver Wulff [mailto:owulff@talend.com] Envoy=E9 : mardi 20 ao=FBt 201= 3 21:14 =C0 : dev@cxf.apache.org Objet : Release Fediz 1.1.0... Hi there I'd like to release CXF Fediz 1.1.0 within the next two weeks. A lot of new= features have been implemented like support for more containers like Jetty= , Websphere 7/8 and Spring Security 2/3 and minor extensions with respect t= o support SAML HoK. The main new feature (FEDIZ-3) for the Fediz IDP is the= support to integrate with other trusted IDPs like ADFS or another Fediz ID= P instance which is connected to another security domain. The following items are pending for 1.1.0: - Feedback and final testing for FEDIZ-3 from Thierry - FEDIZ-34 for Karaf deployment - FEDIZ-46 for CXF JAX-RS support (Sergey, can you work on this?) - FEDIZ-15, IDP supports WS-Federation Metadata document (if I got enough t= ime) - update wiki If you have any other thoughts or objections, let us know. Thanks Oli ------ Oliver Wulff Blog: http://owulff.blogspot.com Solution Architect http://coders.talend.com Talend Application Integration Division http://ww= w.talend.com ________________________________ Ce message et les pi=E8ces jointes sont confidentiels et r=E9serv=E9s =E0 l= 'usage exclusif de ses destinataires. Il peut =E9galement =EAtre prot=E9g= =E9 par le secret professionnel. Si vous recevez ce message par erreur, mer= ci d'en avertir imm=E9diatement l'exp=E9diteur et de le d=E9truire. L'int= =E9grit=E9 du message ne pouvant =EAtre assur=E9e sur Internet, la responsa= bilit=E9 de Worldline ne pourra =EAtre recherch=E9e quant au contenu de ce = message. Bien que les meilleurs efforts soient faits pour maintenir cette t= ransmission exempte de tout virus, l'exp=E9diteur ne donne aucune garantie = =E0 cet =E9gard et sa responsabilit=E9 ne saurait =EAtre recherch=E9e pour = tout dommage r=E9sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely= for the addressee; it may also be privileged. If you receive this e-mail i= n error, please notify the sender immediately and destroy it. As its integr= ity cannot be secured on the Internet, the Worldline liability cannot be tr= iggered for the message content. Although the sender endeavours to maintain= a computer virus-free network, the sender does not warrant that this trans= mission is virus-free and will not be liable for any damages resulting from= any virus transmitted. Ce message et les pi=E8ces jointes sont confidentiels et r=E9serv=E9s =E0 l= 'usage exclusif de ses destinataires. Il peut =E9galement =EAtre prot=E9g= =E9 par le secret professionnel. Si vous recevez ce message par erreur, mer= ci d'en avertir imm=E9diatement l'exp=E9diteur et de le d=E9truire. L'int= =E9grit=E9 du message ne pouvant =EAtre assur=E9e sur Internet, la responsa= bilit=E9 de Worldline ne pourra =EAtre recherch=E9e quant au contenu de ce = message. Bien que les meilleurs efforts soient faits pour maintenir cette t= ransmission exempte de tout virus, l'exp=E9diteur ne donne aucune garantie = =E0 cet =E9gard et sa responsabilit=E9 ne saurait =EAtre recherch=E9e pour = tout dommage r=E9sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely= for the addressee; it may also be privileged. If you receive this e-mail i= n error, please notify the sender immediately and destroy it. As its integr= ity cannot be secured on the Internet, the Worldline liability cannot be tr= iggered for the message content. Although the sender endeavours to maintain= a computer virus-free network, the sender does not warrant that this trans= mission is virus-free and will not be liable for any damages resulting from= any virus transmitted.