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 79EF79F80 for ; Mon, 2 Apr 2012 18:20:41 +0000 (UTC) Received: (qmail 9886 invoked by uid 500); 2 Apr 2012 18:20:41 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 9839 invoked by uid 500); 2 Apr 2012 18:20:41 -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 9831 invoked by uid 99); 2 Apr 2012 18:20:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 18:20:41 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sberyozkin@gmail.com designates 209.85.214.41 as permitted sender) Received: from [209.85.214.41] (HELO mail-bk0-f41.google.com) (209.85.214.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 18:20:34 +0000 Received: by bkwq16 with SMTP id q16so3061549bkw.0 for ; Mon, 02 Apr 2012 11:20:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=RSmbxB+ptKHzHaW86xV4AxnEy9MooPlcc3x/mD1oPnE=; b=d5n+n1YsNSQ3OKA4C9M9cWtD5Rf5+Y9U6YA96ADI4jaM4QS5wjACL+HObrI+ZR5I3C ZPHz1iL+AlX77Unb/Hsk0Q6V7LruqJFsyClz2osWoc5Qh/OwgsRrB/D2egwctHKnq0ry BwQWVNtc6OyergJcXq1mii6av7Uj+cMCqmRMiIXf8OkgJkHSgJ17LgUC5Z83ZW8qpcTh a84rHlbuAgM/XfzUzkeue2v198GIwavyTEE9aFcNMHaPxYk0VUt5rEzZu3WL36GhNEU4 xBanISFss3IcSpQd6HT3ZrZmcJfCIvGurfsERY+XKikLb/bhTnUL0Zvr/2ITQ41SFPzx gTNg== Received: by 10.205.127.130 with SMTP id ha2mr4172208bkc.28.1333390812928; Mon, 02 Apr 2012 11:20:12 -0700 (PDT) Received: from [10.39.0.31] ([87.252.227.101]) by mx.google.com with ESMTPS id jd17sm40396450bkb.4.2012.04.02.11.20.11 (version=SSLv3 cipher=OTHER); Mon, 02 Apr 2012 11:20:12 -0700 (PDT) Message-ID: <4F79EDDA.6050200@gmail.com> Date: Mon, 02 Apr 2012 21:20:10 +0300 From: Sergey Beryozkin User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11 MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Re: Roadmap for fediz in sandbox References: <79AB4452999C844D9920E03635332731120152@S10BE002.SH10.lan> <2519693.v5Csg9gSuX@dilbert.dankulp.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit +1 Sergey On 02/04/12 18:40, Colm O hEigeartaigh wrote: > Sounds good to me as well. So the consensus is it should be a CXF sub-project? > > Colm. > > On Thu, Mar 29, 2012 at 9:58 PM, Daniel Kulp wrote: >> >> Sure. We should likely move it from the sandbox into /cxf/fediz/trunk or >> similar as well. >> >> Dan >> >> >> On Thursday, March 29, 2012 11:18:21 AM Oliver Wulff wrote: >>> Hi all >>> >>> I've initially committed the fediz component to sandbox some months back: >>> http://svn.apache.org/viewvc/cxf/sandbox/fediz/ >>> >>> I'd like to come up with a roadmap for the fediz security component as >>> proposed by Colm in the following mail thread: >>> >>> http://mail-archives.apache.org/mod_mbox/cxf-users/201203.mbox/ajax/%3CCAB >>> 8XdGAKVjb6EVJbccUWyA-nwZci_xKjZ1%3DHXK6XhCUeAjU1vQ%40mail.gmail.com%3E >>> >>> >>> Roadmap >>> ------------- >>> >>> 1st release (end of april): >>> - Move configuration code to fediz-core >>> - Publish WS-Federation Metadata document >>> - Move SignIn request creation to fediz-core >>> - support callback handlers for federation parameters: wauth, whr, >>> >>> 2nd release (end of june): >>> - Create CXF plugin for JAX-RS >>> - Create Websphere plugin based on TAI >>> - Support encrypted token >>> - Support the role of relying party IDP in mock >>> - Support SAML HoK: >>> either use UseKey element in RST >>> or collocate STS in IDP thus STS has access to underlying transport >>> - add layer to support other protocols like SAML-P, OAuth >>> >>> 3rd release (end of september): >>> - create JBoss plugin >>> - create Jetty plugin >>> >>> >>> Do you see any other features? >>> >>> Thanks >>> Oli >>> >>> >>> >>> >>> ------ >>> >>> Oliver Wulff >>> >>> Blog: http://owulff.blogspot.com >>> Solution Architect >>> http://coders.talend.com >>> >>> Talend Application Integration Division >>> http://www.talend.com >> -- >> Daniel Kulp >> dkulp@apache.org - http://dankulp.com/blog >> Talend Community Coder - http://coders.talend.com >> > > > -- Sergey Beryozkin Talend Community Coders http://coders.talend.com/ Blog: http://sberyozkin.blogspot.com