The odd thing is that: curl https://www.google.com/accounts/ClientLogin -d [EMAIL PROTECTED] -d Passwd=secret -d source=Google-cURL-Example -d service=lh2
works like a charm, authentication code and eveything returned perfectly. However when you try to authenticate to the 'ot' service (according to the docs, the open social service): curl https://www.google.com/accounts/ClientLogin -d [EMAIL PROTECTED] -d Passwd=secret -d source=Google-cURL-Example -d service=ot You recieve a 403 status with "Error=BadAuthentication" as document content, according to the doc's this should mean the login/password is invalid. However with some further experimenting it seems that using a random nonsense service name also gives the same BadAuthentication result: curl https://www.google.com/accounts/ClientLogin -d [EMAIL PROTECTED] -d Passwd=secret -d source=Google-cURL-Example -d service=nonsense So it would seem that the 'ot' service isn't registered with the ClientLogin ? Anyone ever had their ClientLogin code working with the 'ot' service? -- Chris On Nov 5, 2007, at 12:55 AM, [EMAIL PROTECTED] wrote: > > Hi Chris, > > After some initial success a lot of us are having difficulties using > the orkut sandbox. The server-side code (orkut/google) isn't > responding, and so all of the opensocial. functions are unavailable > for anyone using javascript gadgets. > > I haven't tried using curl yet but I would suspect that something is > awry on google's end. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
