Difference between revisions of "GVSocialAdapter-Configuration"
| Line 1: | Line 1: | ||
The Social adapter is an adapter which gives {{GVESB}} the ability to interact with social platforms. The configuration is specified into the GVSocialAdapter-Configuration.xml, and the file has the following structure: | The Social adapter is an adapter which gives {{GVESB}} the ability to interact with social platforms. The configuration is specified into the GVSocialAdapter-Configuration.xml, and the file has the following structure: | ||
| + | <syntaxhighlight lang="xml"> | ||
<GVSocialAdapterManager name="GV_SOCIAL" type="module"> | <GVSocialAdapterManager name="GV_SOCIAL" type="module"> | ||
<SocialAdapters> | <SocialAdapters> | ||
| Line 14: | Line 15: | ||
</SocialAdapters> | </SocialAdapters> | ||
</GVSocialAdapterManager> | </GVSocialAdapterManager> | ||
| + | </syntaxhighlight> | ||
The following table explains the configuration: | The following table explains the configuration: | ||
| Line 56: | Line 58: | ||
Social platforms use the OAuth to achieve the following goals: | Social platforms use the OAuth to achieve the following goals: | ||
| − | + | * a user can control which permissions he/she can grant to the installed application | |
| − | + | * a user can revoke such permissions at any time | |
| − | + | * the user's credentials are not spread, the application has its own tokens | |
All the tokens are specified into the configuration file for each account. | All the tokens are specified into the configuration file for each account. | ||
Revision as of 09:41, 21 September 2012
The Social adapter is an adapter which gives GreenVulcano® ESB the ability to interact with social platforms. The configuration is specified into the GVSocialAdapter-Configuration.xml, and the file has the following structure:
<GVSocialAdapterManager name="GV_SOCIAL" type="module">
<SocialAdapters>
<TwitterSocialAdapter class="it.greenvulcano.gvesb.....TwitterSocialAdapter"
social="twitter" type="social-adapter">
<Accounts>
<Account name="PIPPO" consumer_key="..." consumer_secret="..." oauth_access_token="..." oauth_access_token_secret="..." twitteruserid="..."/>
...
</Accounts>
...
<Proxy proxyHost="" proxyPassword="" proxyPort="" proxyUser=""/>
</TwitterSocialAdapter>
</SocialAdapters>
</GVSocialAdapterManager>
The following table explains the configuration:
| Parameter | Meaning and values |
|---|---|
| TwitterSocialAdapter | One of the implemented adapters |
| TwitterSocialAdapter class | the adapter class |
| TwitterSocialAdapter social | the social platform identifier |
| TwitterSocialAdapter type | the adapter type |
| Accounts | wrapper for all the account configured for a single social platform |
| Account | single account configuration |
| Account name | the name identifying the account |
| Account consumer_key | OAuth parameter |
| Account consumer_secret | OAuth parameter |
| Account access_token | OAuth parameter |
| Account access_token_secret | OAuth parameter |
| Account twitteruserid | user id on the social platform |
| Proxy | proxy settings |
| Proxy proxyHost | proxy host |
| Proxy proxyPort | proxy port |
| Proxy proxyUser | user for the proxy |
| Proxy proxyPassword | password for the proxy |
Social platforms use the OAuth to achieve the following goals:
- a user can control which permissions he/she can grant to the installed application
- a user can revoke such permissions at any time
- the user's credentials are not spread, the application has its own tokens
All the tokens are specified into the configuration file for each account.
