[
http://jira.amdatu.org/jira/browse/AMDATUAUTH-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn moved AMDATU-181 to AMDATUAUTH-27:
---------------------------------------------------------
Project: Amdatu Auth (was: Amdatu)
Key: AMDATUAUTH-27 (was: AMDATU-181)
Affects Version/s: 0.1.0
(was: 0.1.0)
Component/s: (was: Amdatu Auth)
Fix Version/s: 0.1.0
(was: 0.1.0)
> Split off oAuth as separate bundle (currently it is contained by the Shindig
> bundle)
> ------------------------------------------------------------------------------------
>
> Key: AMDATUAUTH-27
> URL: http://jira.amdatu.org/jira/browse/AMDATUAUTH-27
> Project: Amdatu Auth
> Issue Type: Task
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Bram de Kruijff
> 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
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
