Hi Jordi Actually, you right, those extra parameters are not treated correctly in 2.5.2, I just checked the source. The code I was referring to would work OK with 2.5.3 (due in a few days), just make sure 'scope' is used, you should be able to confirm it with 2.5.3-SNAPSHOT or check the release vote thread, and use the tagged 2.5.3
Cheers, Sergey On Mon, Apr 16, 2012 at 3:15 PM, Sergey Beryozkin <[email protected]> wrote: > On 16/04/12 14:29, jordi wrote: >> >> Hi Sergey, >> ok, I totally agree what you suggest about URIs, thanks a lot. >> >> Please correct if I'm wrong: as I'm working with OAuth 1.0, I won't be >> able >> to send any scopes information inside the token request. > > As I demonstrated in the code example posted in the previous email it is > possible with the CXF OAuth 1.0 module >> >> To workaround this >> I can migrate my project to OAuth 2.0 in order to use the new standard >> "scope" header, ok? > > If you do not have any specific reasons to work with OAuth 1.0 then I think > starting with 2.0 will be a good idea > > Cheers, Sergey >> >> >> Cheers, >> Jordi >> >> -- >> View this message in context: >> http://cxf.547215.n5.nabble.com/Re-jira-Resolved-CXF-4051-Custom-OAuth-scopes-are-not-supported-tp5643475p5643806.html >> >> Sent from the cxf-user mailing list archive at Nabble.com. -- Sergey Beryozkin http://sberyozkin.blogspot.com Talend - http://www.talend.com
