Hi guys! Last weekend I spent some time debugging my code to have an idea about why I'm getting frequently "authorization failed" or "invalid signature" when authenticating on Orkut using 3LO. The conclusions are:
1) The problem occurs 99% during the process of upgrading an access token. One thing that I noticed is related to access tokens containing scaped characters like '/'. 2) My lib was not using Authorization: OAuth ....... in the header. For some reason it was passing all oauth attributes via querystring (another libs are doing the same), and when changed to the headers, magically, didn't get any errors anymore, which makes me believe that there's an issue on google auth process passing attributes via querystring. 3) Started passing oauth_callback to the authorization header, and also, oauth_verifier, which is required. Tested 10+ times to check if I get the authentication problem, and everything looks fine. Commited a fix few minutes ago, and your help to test it is appreciated. @Tiago @Prasant , any comments ? -Robson Dantas -- You received this message because you are subscribed to the Google Groups "orkut Developer Forum" group. To post to this group, send email to opensocial-or...@googlegroups.com. To unsubscribe from this group, send email to opensocial-orkut+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/opensocial-orkut?hl=en.
