Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of sberyozkin@gmail.com
 designates 74.125.83.47 as permitted sender)
Message-ID: <53145907.3030402@gmail.com>
Date: Mon, 03 Mar 2014 10:27:19 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dev@cxf.apache.org
Subject: Re: OpenId Connect
References: <53121BF0.1090401@hoegernet.de>
In-Reply-To: <53121BF0.1090401@hoegernet.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

Hi Thorsten
On 01/03/14 17:42, Thorsten H�ger wrote:
> Hi,
>
> are there plans to support OpenId Connect (Server/Client) as extension to OAuth2 in CXF?
>
Yes.

Right now, the immediate priority is to support JWT wrapped as CXF 
ServerAccessToken, and the JWT assertions grant. Next, offer the JAX-RS 
services support for the client registration and token management.

OpenId Connect will be next (possibly some prototyping will start after 
the JWT support is done). I'm not sure right now in what form it will be 
supported, may be some of it will be done as part of Fediz, but I think 
at the very least CXF OAuth2 endpoints should be able to work with the 
OpenId Connect aware infrastructure...

Do you have any particular integration requirements ? What is it that 
attracts you in OpenId-Connect most ?

Cheers, Sergey


> Regards,
> Thorsten
>