Nope. Haven't done that with google. I'm doing the container side coding at the moment for a different container implementation ( http://www.lonelyplanet.com/groups ). What we do is give gadget developers a page where they manage their gadget, and part of that gadget admin page is a section for adding/editing/removing oauth credentials.
(Or at least that's how we *will* do it when the code I'm working on right this second for that exact functionality gets checked in and deployed :) ) But like I said, that's container specific, so everyone will implement that in their own way. cheers Julian Doherty 2009/7/8 pablo fernandez <fernandezpabl...@gmail.com> > > Julian, > > Seems like I have to send a mail to google's oauthproxy > (oauthproxy...@google.com)... I've done that but got no reply > > Have you (or anyone in the group) done something like this? have you > registered a third party site to use with google gadgets through > oauth? > > Thanks. > > On Mon, Jul 6, 2009 at 9:30 PM, Julian > Doherty<julian.doherty...@gmail.com> wrote: > > Have a read further down in that document under the "Consumer Key and > > Callback URL" > > at > http://code.google.com/intl/en/apis/gadgets/docs/oauth.html#consumer-key > > Basically, you'll need to generate a twitter oauth key/secret at > http://twitter.com/oauth_clients and > > then submit that somehow to the container where your gadget is hosted. > > Telling the container about the key is done outside the gadget (so as to > > preserve the "secret" part), so it varies from container to container. > > Generally they'll have a web form or email address where you can submit > keys > > to so your gadget can use them. > > Cheers > > Julian Doherty > > > > 2009/7/7 pablo fernandez <fernandezpabl...@gmail.com> > >> > >> Julian, > >> I tried to adapt this example from opensocial docs: > >> http://code.google.com/intl/en/apis/gadgets/docs/oauth.html > >> > >> > I've got the Consumer Key and Consumer Secret from twitter but following that > example I don't know where to put them. > >> Any ideas? > >> > >> On Mon, Jul 6, 2009 at 7:57 PM, Julian Doherty > >> <julian.doherty...@gmail.com> wrote: > >>> > >>> What container are you deploying the gadget to, and have you set up the > >>> consumer key/secret from twitter with the container? > >>> The container needs the credentials as it will make requests to twitter > >>> on your behalf. The way that you get the credentials in there varies > from > >>> container to container. > >>> Cheers > >>> Julian Doherty > >>> > >>> 2009/7/7 Pablo Fernandez <fernandezpabl...@gmail.com> > >>>> > >>>> Hi, I'm developing a simple gadget that interacts with the Twitter > >>>> API, it uses oauth to authenticate with the service provider (twitter > >>>> servers). > >>>> > >>>> here's the code for the gadget via pastie: http://pastie.org/536055 > >>>> > >>>> I put a breakpoint in firebug to see the result, but twitter servers > >>>> throw a 403 (unauthorized) response.... > >>>> > >>>> What am I doing wrong? > >>>> > >>> > >>> > >>> > >> > >> > >> > >> -- > >> Fernandez, Pablo. > >> > >> > > > > > > > > > > > > > -- > Fernandez, Pablo. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" group. To post to this group, send email to opensocial-api@googlegroups.com To unsubscribe from this group, send email to opensocial-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
