Implement pluggable and centralized context management service
--------------------------------------------------------------
Key: AMDATU-247
URL: http://jira.amdatu.org/jira/browse/AMDATU-247
Project: Amdatu
Issue Type: Task
Components: Amdatu Auth
Affects Versions: 0.1.0
Reporter: Ivo Ladage - van Doorn
Fix For: 0.1.0
The following issues describe context-related issues in Amdatu:
http://jira.amdatu.org/jira/browse/AMDATU-84
http://jira.amdatu.org/jira/browse/AMDATU-245
http://jira.amdatu.org/jira/browse/AMDATU-246
Each of these issues refer to the need of context information, sometimes a
'username' and in other cases a 'tenantid'. The issues described some possible
solutions which have obvious drawbacks:
- Passing context information in method invocations, over and over again
- Retrieving context information from a HTTP request
Now while these issues only describe the contextual information 'username' and
'tenantid', it is likely that more context information is required in the
future. For example the OpenSocial context is represented by a security token,
which contains a viewerid, ownerid but also an expiry date of the context. So a
similar approach should be available in Amdatu and it should satisfy the
following requirements:
- Context is always available, without the need of passing a HTTP request
- The context is pluggable; any component may add a piece of information to the
context (like Shindig adding a OpenSocial context, containing the viewerid and
ownerid)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
