Hello Andrew, Have you tried using OAuth Playground<http://googlecodesamples.com/oauth_playground/>to debug your issue? You can set your own consumer key and secret, choose the signature method, etc. and compare the difference between the requests sent to the authorization servers by OAuth Playground<http://googlecodesamples.com/oauth_playground/>and your application.
Best, Alain On Mon, Oct 24, 2011 at 4:18 PM, Andrew Horsman <[email protected]>wrote: > I have some Ruby code here, https://gist.github.com/1310680 which attempts > to get a request token. After debugging some initial issues I've gotten > down to a signature_invalid error (with a 400 status code). > > According to the OAuth specification ( > http://oauth.net/core/1.0/#signing_process) my method of generating the > signature appears to be correct. Comparing to the samples here, > http://code.google.com/apis/accounts/docs/OAuth_ref.html#RequestToken my > signature base *appears *to be correct however I'm thinking the issue is a > malformed signature base. > > -- > You received this message because you are subscribed to the Google > Groups "Google Calendar Data API" 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://code.google.com/apis/calendar/community/forum.html > -- Alain Vongsouvanh | Developer Programs Engineer -- You received this message because you are subscribed to the Google Groups "Google Calendar Data API" 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://code.google.com/apis/calendar/community/forum.html
