-
Type:
Suggestion
-
Resolution: Fixed
-
Component/s: Dashboard & Gadgets
-
None
While the SAL implementation of these SPI's is sufficient for summit, for production we'll probably wont something more robust that doesn't store everything in propertysets. Namely I'll implement these natively in JIRA:
- Consumer token store
- Service provider consumer store
- Service provider token store
There's a few open questions regarding this still:
- Is there a limit on the key length used for tokens/consumers? (so we can limit the PK in the db to speedup lookups)
- How will these tables get cleaned up? Probably will need to add a 'last-used' timestamp in the db, so that we can write a background service to clean these columns up in the future.
- details
-
JRASERVER-16927 Implement consumer Oauth token store
-
- Closed
-
-
JRASERVER-16928 Implement Service Provider TokenStore
-
- Closed
-
-
JRASERVER-16929 Implement Service Provider ConsumerStore
-
- Closed
-
-
JRASERVER-17687 Finish OAUTH persistence and write unit tests
-
- Closed
-