You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Ryan Baxter (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/02 21:47:35 UTC

[jira] [Resolved] (SHINDIG-1601) Enhance Gadget Administration

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

Ryan Baxter resolved SHINDIG-1601.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.0

Committed revision 1178236.
                
> Enhance Gadget Administration
> -----------------------------
>
>                 Key: SHINDIG-1601
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1601
>             Project: Shindig
>          Issue Type: New Feature
>    Affects Versions: 3.0.0
>            Reporter: Ryan Baxter
>             Fix For: 3.0.0
>
>         Attachments: issue-1601.patch
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> We want to add some administration features to Shindig.  This patch adds/changes 3 things in Shindig.
> 1.  Remove the existing blacklist functionality in Shindig which currently is enabled by pointing Shindig to a text file with a list of gadgets to blacklist.  The new functionality uses a whitelist instead of a blacklist and is indexed on a per container basis.  Meaning an admin could whitelist some gadgets in one container but not another.  This functionality is enabled through a Guice module allowing implementors to use something else besides a text file.
> 2.  Add the ability for administrators to specify which features are allowed and denied for a specific gadget in a specific container.  This information is checked in two places, when the metadata request is made and when the gadget is rendered.
> 3.  Add the ability for containers to secure RPC requests made by gadgets.  The RPC code now has the ability to arbitrate all RPC calls made.  Containers can specify their own arbitrator.  The common container has its own default arbitrator available.

--
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