[RAVE-82] OAuth persistent implementation

• Type: Umbrella
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.3-INCUBATING
• Component/s: build & development
• Assignee: Unassigned
• Reporter: Okke Harsta
• Created: 22/Jun/11 11:28
• Updated: 27/Oct/11 15:36

Description

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).

Issue Links

• incorporates: RAVE-20 Implement container/shindig auth

Sub-Tasks

• Provide a way to override properties from shindig.properties: Closed
• Oauth key and secrets need to be maintainable (and secure): Closed
• Persistent OAuth request tokens: Closed
• Use 'new' Spring JPA pattern for OAuth persistency: Closed