[
https://issues.jboss.org/browse/SEAMSOCIAL-12?page=com.atlassian.jira.plu...
]
Antoine Sabot-Durand commented on SEAMSOCIAL-12:
------------------------------------------------
The problem is that OAuth information are stored in OAuthService bean today. The should be
separated, so we could have more than one and the information would be easier to persist.
Allow the support of multi-account on a given social service
------------------------------------------------------------
Key: SEAMSOCIAL-12
URL:
https://issues.jboss.org/browse/SEAMSOCIAL-12
Project: Seam Social
Issue Type: Enhancement
Components: OAuth Core
Reporter: Antoine Sabot-Durand
Assignee: Antoine Sabot-Durand
Priority: Minor
Original Estimate: 3 days
Remaining Estimate: 3 days
It would be nice to support multi-account for a given social service (my personal Twitter
account and my company's one).
Since it can have an important impact on API design, the hook for this evolution should
be created now to be sure we can go in this direction in the futur.
The best would be to keep the standard behavior (single account for a service) as simple
as today.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira