[
https://issues.apache.org/jira/browse/WOOKIE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484465#comment-13484465
]
Hoang Minh Tien commented on WOOKIE-390:
----------------------------------------
implemented from r1402319
The creation of widget is similar to implicit grant, the following parameters
need to be declared in config.xml:
* profile : is "authorization code" (default value is implicit)
* clientId : client identifier provided by service provider (facebook, buffer,
google ...)
* clientSecret : client secret string (sometime called API key) provided by
service providers
* authzServer: authorization endpoint, an url defined by service providers
* tokenEndpoint : token endpoint, an url defined by service provider
* persist : optional (default is true) same meaning as using in implicit grant.
The redirect url registered to service provider with this profile has following
form: http://your.wookie.server/wookie/features/oauth/authz-code
May be Ross would want to continue with buffer widget that you mentioned long
time ago :-). Here is some guide line I got from buffer
* manual http://bufferapp.com/developers/api/oauth
* authzServer: https://bufferapp.com/oauth2/authorize
* tokenEndpoint: https://api.bufferapp.com/1/oauth2/token.json
* clientId and clientSecret will be provided when you register an application
with buffer and don't forget to set redirect url to correct upper value
> Adding oauth authorization code grant support to widget
> -------------------------------------------------------
>
> Key: WOOKIE-390
> URL: https://issues.apache.org/jira/browse/WOOKIE-390
> Project: Wookie
> Issue Type: Improvement
> Components: Feature Management
> Reporter: Hoang Minh Tien
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
