[ 
https://issues.apache.org/jira/browse/WOOKIE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135785#comment-13135785
 ] 

Scott Wilson commented on WOOKIE-100:
-------------------------------------

Thanks Tien - I added the <access> config for a single widget rather than 
adding to the global whitelist as this is how I imagine it would have to work 
in practice (or the admin would have to manually edit the global whitelist for 
every oAuth-capable widget). I've tried it both ways round and get the same 
effect.

One other thing I noticed was an X-Frame security alert in Safari:

Refused to display document because display forbidden by X-Frame-Options.

Also, if I reset the browser (clearing cookies) and start from scratch, I never 
get beyond the profile page without manually refreshing the browser. So it 
would be worth testing from a clean start in case that shows up the problem.
                
> 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
>              Labels: gsoc, mentor
>             Fix For: 0.9.2, 0.9.3
>
>         Attachments: WOOKIE-WookieOpenIDsupport-110711-0506-358.pdf, 
> WOOKIE_OPENID_AUTH_FLOW.png, hogwarts.info.fundp.ac.be, oAuthClient.java, 
> oauth_092_patch.txt, wookie-oauth.zip
>
>
> 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 proposal (see attached file)
> [1] http://markmail.org/thread/qyjhlm2f3v3cben5

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to