On Jan 30, 2008 11:44 AM, Reinoud Elhorst <[EMAIL PROTECTED]> wrote: > Problem is that only the container-webpage knows whether this permission has > been obtained (in the general case, obviously sometimes the permission is > always granted or denied). So either the call needs to go through the > container page, or the gadget needs to have some token that affirms that it > has access to the viewer_id (or viewer_whatever), which needs to be checked > by the gadget server.
OK, I think the answer to this question is that the container and the gadget server need to collaborate closely. If the gadget server has enough information to validate and decrypt the security token it is already tightly coupled (sharing keys) with the container. They need to have a common understanding of policy as well. There's more than one way to pass that policy information between the container and the gadget server. Depending on how much information there is it might fit into the security token, or you might want to have them share a backend data store that they use to reference policy. Cheers, Brian
