Details
-
Type:
Enhancement
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: OAuth Core
-
Labels:None
Description
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.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
I start the task by putting all the services bean to dependent scope and created a qualifier (@RelatedTo) and an enum class Service listing all the services to allow bean selection for a given service. Thus it's now possible to get more than one bean for each services.
The OAuthSettings is now in @ApplicationScope since we support out of the box only one OAuth application settings by service. The configuration file will add qualifiers and value to create effective OAuthServiceSettings beans.
Antoine Sabot-Durand
added a comment - I start the task by putting all the services bean to dependent scope and created a qualifier (@RelatedTo) and an enum class Service listing all the services to allow bean selection for a given service. Thus it's now possible to get more than one bean for each services.
The OAuthSettings is now in @ApplicationScope since we support out of the box only one OAuth application settings by service. The configuration file will add qualifiers and value to create effective OAuthServiceSettings beans. 
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.