Hi Martin,
I had a similar question regarding the OAuth2.0 and Jersey.
Is there a roadmap for getting this support in Jersey?
I see many providers like Facebook moving to / using OAuth2.0. It would be
great to have support for this in Jersey.
Thanks,
Naresh
On Sat, Feb 5, 2011 at 1:49 AM, Martin Matula <martin.matula_at_oracle.com>wrote:
> Hi Girish,
>
>
> On 4.2.2011 20:15, Girish Khadke wrote:
>
>
> I have following questions:
>
> 1. I am using 1.1.5 API and I want to know does it support OAuth 2.0 ??
> (because all the examples they have given for PHP and Python use some
> Oauth2 libraries on Github)
>
> We don't have any special support for OAuth 2.0 - the Jersey OAuth
> libraries support OAuth 1.0.
> Anyway, I don't think your app is using OAuth 2.0 - that spec is not final
> yet and none of the drafts that were out there had a notion of consumer
> secret and token secret as far as I know. That's a concept used in OAuth
> 1.0.
> I know there were some bugs in the earlier versions of the libraries, so
> you may want to try the latest (version 1.5).
> Also, it would be interesting to see how the headers of the messages the
> python client library sends look like.
>
>
> 2. Also the basic Server side web service is all written in Python and it
> supports JSON and plain text. ( I went through source code of Stashboard
> located at folder /handler in installation directory written as script
> restful.py)
>
> Now since the Server side web service is in Python and still I should
> be able to consume and post JSON objects from it right?
>
> Yes.
>
> Martin
>
>