You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Brian Eaton (JIRA)" <ji...@apache.org> on 2008/04/29 18:23:56 UTC
[jira] Created: (SHINDIG-218) implement locked domain
implement locked domain
-----------------------
Key: SHINDIG-218
URL: https://issues.apache.org/jira/browse/SHINDIG-218
Project: Shindig
Issue Type: Bug
Reporter: Brian Eaton
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.
[jira] Issue Comment Edited: (SHINDIG-218) implement locked domain
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593044#action_12593044 ]
beaton edited comment on SHINDIG-218 at 4/29/08 11:25 AM:
---------------------------------------------------------------
The base32 encoding is from Neal Gafter. The LockedDomainService interface and HashLockedDomain implementation are from Kevin Brown. Any bugs are mine.
was (Author: beaton):
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.
[jira] Updated: (SHINDIG-218) implement locked domain
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (SHINDIG-218) implement locked domain
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cassie Doll closed SHINDIG-218.
-------------------------------
Resolution: Fixed
Assignee: Cassie Doll
> implement locked domain
> -----------------------
>
> Key: SHINDIG-218
> URL: https://issues.apache.org/jira/browse/SHINDIG-218
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Assignee: Cassie Doll
> 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.