I have managed to play with my code and I have found that oauth_token was previously used int the base string as an empty value whereas now it is complitely omitted. Just making sure that my code does not force the oauth_token parameter in the base string gets my code up and running again.
Although I think there have been some more changes related to the normalisation of parameters as to when they should be urlencoded or not to match the signature Opensocial_app_url should not really make any difference as it is just another custom parameter, it could have been any parameter needed from your application. Opensocial_app_url would have characters like http:// that will need to be escaped and this could cause issues in verification code. Once I solve all the issues with the dilemma of escaping or not I'll post my code Marco On Oct 3, 9:59 am, Nemesh <[EMAIL PROTECTED]> wrote: > Hello Jason, > > I saw the variables appended to the URL upon signing request has > changed. I see a new variable "opensocial_app_url". I am not sure if > it existed earlier also. So there might be something which has changed > in opensocial API. Can anyone confirm this? > > Nemesh > > On Oct 3, 1:37 am, csharpsocial <[EMAIL PROTECTED]> wrote: > > > > > Ok, I'll give it a go... > > it looks like the problem would reside in the ouathbase class that we > > all kind of share > > considering it is downloadable from the wiki, and considering that my > > code differs from > > Nemesh code only on the certificate handling. > > I'll keep you posted on the progress > > > Marco > > > On Oct 2, 1:40 am, Jason <[EMAIL PROTECTED]> wrote: > > > > Thanks Marco. Can you test the source in the thread I linked to > > > previously while I work to verify the problem with yours? > > > > - Jason > > > > On Oct 1, 1:46 pm, csharpsocial <[EMAIL PROTECTED]> wrote: > > > > > Hi Jason, > > > > I have sent you a test app with the code. > > > > > Thanks for your help > > > > > Marco > > > > > On Oct 1, 7:24 pm, Jason <[EMAIL PROTECTED]> wrote: > > > > > > Are all of you using custom (e.g. in-house, self-written) C# > > > > > validation code or is there a shared routine for .NET back-ends. It's > > > > > somewhat disconcerting that this would break suddenly in such a > > > > > limited way (the PHP code provided in the wiki seems to work, so it's > > > > > not an issue with the public key), but it's also clear that there is > > > > > something going on. > > > > > > Feel free to send me your source and I'll look into it straightaway, > > > > > but you may also want to take a look at this thread in the meantime > > > > > which has a complete C# validation routine (towards the bottom of the > > > > > post) that the developer indicates is working: > > > > > >http://groups.google.com/group/opensocial-orkut/browse_thread/thread/... > > > > > > - Jason > > > > > > On Sep 29, 11:32 pm, Raman <[EMAIL PROTECTED]> wrote: > > > > > > > Yes, ditto. > > > > > > I have a live app running on orkut (or should I say, it was). Coz, > > > > > > my dot > > > > > > net code is not able to authenticate the requests from Orkut > > > > > > anymore. Whats > > > > > > the issue? What have been changed? > > > > > > > Raman- Hide quoted text - > > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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-orkut@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-orkut?hl=en -~----------~----~----~----~------~----~------~--~---
