OAuth persistent implementation
-------------------------------
Key: RAVE-82
URL: https://issues.apache.org/jira/browse/RAVE-82
Project: Rave
Issue Type: Umbrella
Components: build & development
Affects Versions: 0.2-INCUBATING
Reporter: Okke Harsta
Assignee: Okke Harsta
Fix For: 0.2-INCUBATING
The default implementation in shindig for all OAuth related functionality is
using an in-memory store for request tokens, a dummy implementation for
checking the security token and the key/secrets are stored in a json file. In
order to implement this production-worthy using a persistent (e.q. rdbms)
datastore some additional changes are also required like providing a hook to
override properties in shindig.properties (now located in shindig-common/conf)
and properly securing shindig.
This umbrella issue is used to link all various issues related to the proper
implementation (2-legged and 3-legged where Rave can act as both OAuth consumer
on behalf of gadgets and act as OAuth provider).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
