[jira] Updated: (WOOKIE-85) Implement W3C Widget Access Request Policy (WARP) specification

["Scott Wilson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WOOKIE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Wilson updated WOOKIE-85:
-------------------------------

    Attachment: warp.txt

I've attached a patch of the server code; this does not include the changes to DB scripts and test cases.

> Implement W3C Widget Access Request Policy (WARP) specification
> ---------------------------------------------------------------
>
>                 Key: WOOKIE-85
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-85
>             Project: Wookie
>          Issue Type: New Feature
>          Components: Configuration, Documentation, Server, Web Admin
>            Reporter: Scott Wilson
>            Assignee: Scott Wilson
>             Fix For: 0.8.1
>
>         Attachments: warp.txt
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> The WARP spec defines an additional element in the Widget config.xml that enables a widget author to indicate that a widget requires access to network resources. This includes the wildcard (*) that indicates arbitrary access (e.g. for a generic RSS widget).
> http://dev.w3.org/2006/waf/widgets-access/
> To implement this specification requires modification of the Whitelist functionality in Wookie:
> - allow per-widget access rules rather than global rules
> - an extra part of the GUI to alert admins to access request elements when installing new widgets through the admin interface, and allow them to allow or reject such requests being added to the policy set
> - a server property that sets whether access requests should be immediately added to the policy set when installing widgets using hot deploy.
> - updated whitelist manager GUI

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.