[
http://jira.amdatu.org/jira/browse/AMDATU-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10296#comment-10296
]
Ivo Ladage - van Doorn edited comment on AMDATU-181 at 11/16/10 11:39 AM:
--------------------------------------------------------------------------
Splitting off oAuth from shindig would mean that we also need to split off the
gadget store from shindig, since the oAuth service will need to communicate
with the gadgetstore to verify consumer keys and secrets. Alternatively, a
oAuth store could be added that only contains oAuth enabled Amdatu services as
opposed to storing all (including external) gadgets.
oAuth should be completely independent from opensocial/shindig/gadgets etc.
since we want to use oAuth for all (REST) services in the future.
was (Author: ivol):
Splitting off oAuth from shindig would mean that we also need to split off
the gadget store from shindig, since the oAuth service will need to communicate
with the gadgetstore to verify consumer keys and secrets. Alternatively, a
oAuth store could be added that only contains oAuth enabled Amdatu gadgets as
opposed to storing all (including external) gadgets.
> Split off oAuth as separate bundle (currently it is contained by the Shindig
> bundle)
> ------------------------------------------------------------------------------------
>
> Key: AMDATU-181
> URL: http://jira.amdatu.org/jira/browse/AMDATU-181
> Project: Amdatu
> Issue Type: Task
> Components: Amdatu OpenSocial
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.1.0
>
>
> The oAuth servlet (and service in the future) should be moved to a separate
> oAuth bundle. Currently it is embedded in the Shindig service. This should
> facilitate the use of the oAuth standard for authentication without the need
> of having the whole Shindig container deployed.
> Note that it would be even better to split off oAuth support from the Shindig
> implementation completely, such that it can be moved to the web project for
> example without any opensocial/shindig dependencies. However, the current
> oAuth implementation embedded in Shindig off course depends on many Shindig
> specific classes, so that wouldn't be easy without embedding certain shindig
> libraries. An alternative approach could be to use a different oAuth library
> for oAuth support, for example net.oauth or Scribe.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
