On Tue, May 26, 2009 at 10:52 AM, Chirag <[email protected]> wrote:
> > When consumers encounter the infamous signature_invalid error, it's > often useful to compare the signature base string[1] generated by the > service provider with what the consumer generated. > > When looking at the problem-reporting "extension" [2], the > signature_invalid section should encourage service providers to > include the signature base string used to calculate the signature in > the error response. > > If the service provider does not provide this information, the > consumer is often guessing where the issue lives. > > [1] - http://oauth.net/core/1.0/#anchor14 > [2] - http://wiki.oauth.net/ProblemReporting > > Thanks, > Chirag Shah > > The Python OAuth library already includes the expected base string in the error response. What API or library are you concerned about? Feel free to file tickets against libraries here: http://code.google.com/p/oauth/issues/list Thanks, Leah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" 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/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
