Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 23 Jan 2012 11:04:40 +0000 (UTC)
From: "Sergey Beryozkin (Resolved) (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <987563192.66328.1327316680061.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1102342118.65085.1327270359815.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CXF-4051) Custom OAuth scopes are not supported
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin resolved CXF-4051.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6
                   2.5.3
    
> Custom OAuth scopes are not supported
> -------------------------------------
>
>                 Key: CXF-4051
>                 URL: https://issues.apache.org/jira/browse/CXF-4051
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>             Fix For: 2.5.3, 2.6
>
>
> Clients can include custom scopes ("x-oauth-scope" in CXF (OAuth 1.0 extension), "scope" in OAuth 2.0).
> This does not get passed via Authorization header, mainly due to the bug in the Google lib.
> Another bug is that on the server side the custom form payload is assumed to be part of the OAuth payload. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira