[
https://issues.apache.org/jira/browse/WOOKIE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865626#action_12865626
]
Scott Wilson commented on WOOKIE-100:
-------------------------------------
Note also there is a proposal in the incubator for a common oAuth
implementation to use across Apache projects [1].
I've had some progress on using the Signpost oAuth implementation [2] with
services like Twitter. However, the major architectural issue is how consumer
keys and secrets are managed. These cannot be distributed with the widget
itself; one option is for Wookie to store these separately and have the Wookie
admin apply for a consumer key/secret for each widget that needs it. Its a bit
time consuming, but I can't think of an easier workaround.
[1] http://wiki.apache.org/incubator/AmberProposal
[2] http://code.google.com/p/oauth-signpost/
> Open ID/OAuth Support
> ---------------------
>
> Key: WOOKIE-100
> URL: https://issues.apache.org/jira/browse/WOOKIE-100
> Project: Wookie
> Issue Type: New Feature
> Reporter: Ross Gardler
> Priority: Minor
>
> OpenID support for widgets would be really useful, as suggested by Bernhard
> Hoisl. [1]
> Bryan Copeland indicated that he has already done some OpenID/OAuth work and
> has provided a very useful wiki page to document this. [2]
> [1] http://markmail.org/thread/qyjhlm2f3v3cben5
> [2] http://cwiki.apache.org/confluence/display/WOOKIE/Wookie+OpenID+support
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
