[
http://jira.amdatu.org/jira/browse/AMDATUOPENSOCIAL-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11598#comment-11598
]
Ivo Ladage - van Doorn commented on AMDATUOPENSOCIAL-114:
---------------------------------------------------------
The consumer secret in the gadget definition is only used when the gadgetspec
defines OAuth in its ModulePrefs. The 3-legged OAuth example gadget in the auth
subproject is the only gadget actually using this. One could argue if consumer
secrets should be gadget specific. It would make sense that all gadgets use the
same consumer key and secret; the one of the gadget container.
Furthermore, Shindig itself is of course not multi-tenant. Effectively this
means that there can be only one OAuthStore, as this is bound in the Guice
module. So how do we implement multi-tenancy in a single OAuthStore? That may
be an issue...
> Make gadget repository tenant-aware
> -----------------------------------
>
> Key: AMDATUOPENSOCIAL-114
> URL: http://jira.amdatu.org/jira/browse/AMDATUOPENSOCIAL-114
> Project: Amdatu OpenSocial
> Issue Type: Improvement
> Components: Gadget management
> Reporter: Ivo Ladage - van Doorn
> Fix For: 0.2.0
>
>
> The current gadget repository is not tenant aware. In a tenant aware
> solution, it would be possible to manage gadgets and categories per tenant.
> Design is needed on how this would work when adding gadgets manually and
> using the whiteboard style registration of gadgets.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
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
