OK I understand. Quickly looking at the TODO gadgets source it looks like they are using signed fetch (2 legged OAuth). Personally this is one of the areas I am not familiar with in Shindig, so I can't be to much help on how to enable it, maybe someone else knows more.
However I believe you will need to reach out to the OAuth provider (in this case the authors of the TODO gadget) to exchange some information with them in order to make this work. OAuth generally involves some exchange of information between the client (the container) and the provider. On Tue, Oct 1, 2013 at 3:43 PM, Darren Bond <db...@globalcad.com> wrote: > Hi Ryan, > > > > Please find below a further description and links to our new test site. > > > > Certain gadgets interact with users and during that interaction silently > save such user generated data, an example being the To Do List gadget... > > http://www.google.com/ig/directory?type=gadgets > <http://www.google.com/ig/directory?type=gadgets&url=www.labpixies.com/campa > igns/todo/todo.xml> &url=www.labpixies.com/campaigns/todo/todo.xml > > According to our research, such gadgets use the OAuth mechanism for > communication between the gadget container (Shindig) and the gadget's > internal infrastructure which is encapsulated on the gadget's server side. > We have no clue regarding how to integrate such a configuration with our > site and to persist such user data. > > > > Essentially, if a user enters notes on the To Do List and then closes and > loads the page again, such data is lost. This also appears to happen on the > iGoogle site for anonymous visitors. However, for registered users (logged > in) the To Do notes are preserved and restored between browser sessions - so > the question is, how can we do the same on our site and preserve this data > between browser sessions? > > > > We've generated a test site for problem gadgets, including the To Do List > gadget issued mentioned above... > > > > http://beta.blueg.com/test/personal.htm > > http://beta.blueg.com/test/personal_canvas.htm > > > > Kind regards, > > > > Darren >
