Hi Brian, Gadget features can be secured via the gadget administration functionality that was added to Shindig 3.0 a while back. Here's the JIRA: https://issues.apache.org/jira/browse/SHINDIG-1601
This functionality is turned off by default and you would need to enable it in your container.js via gadgets.admin.enableFeatureAdministration. The default configuration is handled in /shindig-project/config/gadget-admin.json and there's some sample data in there. If gadget administration is enabled then at gadget load time the Shindig server won't serve up the JavaScript for a feature for a gadget unless it is configured to allow it. If you want to dig around in the code you can find the vast majority of it in the org.apache.shindig.gadgets.admin package in Shindig. -Stanton From: Henry Saputra <[email protected]> To: [email protected], Cc: [email protected] Date: 02/14/2012 22:32 Subject: Re: Securing Gadget Features Hi Brian, There is a way to add custom features to Shindig but I dont remember if there is an built-in mechanism to filter which gadgets could have access to that features. Any gadget definition could simply add <Require> or <Optional> to include features so I think the easiest way to prevent this is through your gadget registration flow? - Henry On Tue, Feb 14, 2012 at 7:15 PM, Brian McCullars <[email protected]> wrote: > Is there a way to add a custom feature to Shindig and only have specific > gadgets access that feature? > > -- > Brian McCullars > Mobile (513) 549-3099 > Home (513) 549-5884
