[
https://issues.apache.org/jira/browse/WOOKIE-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864872#action_12864872
]
Scott Wilson commented on WOOKIE-142:
-------------------------------------
One solution is for Wookie to manage consumer keys and secrets for widgets
(i.e. each Wookie server needs to register each widget it serves) and then have
these accessed by oAuth middleware.
I've got bits of a working solution using SignPost, but didn't really want to
check it into the core yet.
> Twitter API Widget
> ------------------
>
> Key: WOOKIE-142
> URL: https://issues.apache.org/jira/browse/WOOKIE-142
> Project: Wookie
> Issue Type: Improvement
> Reporter: Bryan Copeland
> Priority: Trivial
> Attachments: twitter.wgt
>
>
> This is just a first stab to extending the same methods as Flickr and YouTube
> widgets into Twitter...
> It works for read only right now (search by Tweet text or User tweets)
> For Tweeting/status updates, there is a slight problem with the
> authentication in the OAuth signing directly from Javascript via the OAuth JS
> library, so, this may be one case of a widget which does require a
> server-side OAuth proxy to relay access tokens securely (although, I have
> seen Yahoo! YQL used to authenticate remotely to Twitter, so it may still be
> possible)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
