[
http://jira.amdatu.org/jira/browse/AMDATU-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10613#comment-10613
]
Ivo Ladage - van Doorn edited comment on AMDATU-84 at 1/5/11 4:21 PM:
----------------------------------------------------------------------
Although making UserAdmin is fairly simple, an approach is needed to resolve
the proper UserAdmin to use dependent on some tenant related information (like
a hostname for example). Code that depends on UserAdmin:
- Login service / Login REST service
- User admin REST service / User admin gadget
- Shindig appdata store
>From these examples it is clear that this is not as simple as it may seem:
- How does a REST service know what UserAdmin service it needs to invoke? A
REST service itself cannot be tenant specific, as it is invoked by Wink which
is not tenant aware (nor OSGi aware).
- How does the Shindig appdata store know what UserAdmin service it needs to
invoke? Shindig is not tenant aware and so the shindig API's do not pass any
information about the tenant. Maybe the info could be added to the security
token, but the SecurityToken is not pluggable and the SecurityToken is only
available in a few methods. It is not available in getPerson, getuser,
setFriends and getFriends for example.
- How does the Login service knows the tenant? Should the tenant be passes as
input argument for login/logout?
>From these examples it is clear that we need to have some generic/pluggable
>mechanism for tenant resolving. This is covered by issue
>http://jira.amdatu.org/jira/browse/AMDATU-245
was (Author: ivol):
Although making UserAdmin is fairly simple, an approach is needed to
resolve the proper UserAdmin to use dependent on some tenant related
information (like a hostname for example). Code that depends on UserAdmin:
- Login service / Login REST service
- User admin REST service / User admin gadget
- Shindig appdata store
>From these examples it is clear that this is not as simple as it may seem:
- How does a REST service know what UserAdmin service it needs to invoke? A
REST service itself cannot be tenant specific, as it is invoked by Wink which
is not tenant aware (nor OSGi aware).
- How does the Shidnig appdata store know what UserAdmin service it needs to
invoke? Shindig is not tenant aware and so the shindig API's do not pass any
information about the tenant. Maybe the info could be added to the security
token, but the SecurityToken is not pluggable and the SecutirtyToken is only
available in a few methods. It is not available in getPerson, getuser,
setFreinds and getFriends for example.
- How does the Login service knows the tenant? Should the tenant be passes as
input argument for login/logout?
>From these examples it is clear that we need to have some generic/pluggable
>mechanism for tenant resolving. This is covered by issue ...
> User Profiles are not tenant specific
> -------------------------------------
>
> Key: AMDATU-84
> URL: http://jira.amdatu.org/jira/browse/AMDATU-84
> Project: Amdatu
> Issue Type: Improvement
> Components: Amdatu OpenSocial
> Affects Versions: 0.0.4
> Reporter: Dion Meijer
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.1.0
>
>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
