You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2009/12/11 14:58:18 UTC
[jira] Created: (WOOKIE-85) Implement W3C Widget Access Request
Policy (WARP) specification
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
Fix For: 0.8.2
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.
[jira] Updated: (WOOKIE-85) Implement W3C Widget Access Request
Policy (WARP) specification
Posted by "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.
[jira] Commented: (WOOKIE-85) Implement W3C Widget Access Request
Policy (WARP) specification
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839850#action_12839850 ]
Scott Wilson commented on WOOKIE-85:
------------------------------------
This has now been committed. Any widget deployed using the build scripts, or by dropping the .wgt file into the local deploy folder automatically have any access requests granted by Wookie (a message is generated in the log/console stating which widget has been granted access, and the origin it applies to).
However this is not implemented for widgets added through the web interface; nor is there any management UI for admins to manually grant or revoke access requests.
> 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.
[jira] Work logged: (WOOKIE-85) Implement W3C Widget Access Request
Policy (WARP) specification
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_11016 ]
Scott Wilson logged work on WOOKIE-85:
--------------------------------------
Author: Scott Wilson
Created on: 25/Mar/10 09:58 AM
Start Date: 25/Mar/10 09:58 AM
Worklog Time Spent: 8h
Work Description: Implementing WARP spec
Issue Time Tracking
-------------------
Time Spent: 8h
Remaining Estimate: 0h (was: 8h)
> 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
> Time Spent: 8h
> Remaining Estimate: 0h
>
> 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.