[
https://issues.apache.org/jira/browse/SHINDIG-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Chabot resolved SHINDIG-537.
----------------------------------
Resolution: Fixed
Assignee: Chris Chabot
Full support for 2 legged and 3 legged OAuth was committed about a week ago.
Special thanks to Joseph Smarr for helping out with this, he did the OAuth
magic, and I just tied it into shindig and partuza :)
> OAuth server support for RESTful Interface
> ------------------------------------------
>
> Key: SHINDIG-537
> URL: https://issues.apache.org/jira/browse/SHINDIG-537
> Project: Shindig
> Issue Type: New Feature
> Components: RESTful API (PHP)
> Reporter: Chris Chabot
> Assignee: Chris Chabot
> Priority: Blocker
>
> See subject.
> Currently php shindig uses a GadgetToken to retrieve the owner/viewer/mod
> id/app id information, this should be complimented with an OAuth based one
> (both inheriting from the same SecurityToken class), which provides the same
> information but then based on the OAuth authentication.
> This way it should be completely transparent to the underlying code if this
> is an oauth or gadget token based request, which should make life easier for
> people implementing the service adapters.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
