[
https://issues.apache.org/jira/browse/SHINDIG-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Eaton updated SHINDIG-218:
--------------------------------
Attachment: locked-domain.patch
The base32 encoding is from Kevin Graff. The LockedDomainService interface and
HashLockedDomain implementation are from Kevin Brown. Any bugs are mine.
> implement locked domain
> -----------------------
>
> Key: SHINDIG-218
> URL: https://issues.apache.org/jira/browse/SHINDIG-218
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: locked-domain.patch
>
>
> If two gadgets can render on the same domain, they can see each other's data.
> The attached patch implements locked-domain for Shindig, using the same
> syntax that iGoogle uses:
> http://code.google.com/apis/gadgets/docs/reference.html#lockeddomain
> The configuration in this patch disables locked-domain, since most people
> don't have wildcard DNS on their development machines.
> Edit java/gadgets/conf/gadgets.properties to enable the locked domain feature.
> Once you've changed that configuration, you can either enable locked domain
> for all gadgets on a particular container, or allow gadget authors to opt-in
> to the feature with <require feature="locked-domain"/> in their gadgets.
> To enable locked-domain for a particular container, edit the container.js
> file to set gadgets.lockedDomainRequired = true.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
