My space is returning and improper signature from the makerequest call. There is definitely issue with encoding of the url. When using the Oauth Tool myspace gives me the same signature and basestring that I expect. However when using makerequest myspace is delivering an invalid signature because it...

Hi, We were trying to get the authenication working... but still no luck! I saw many posts here on the same subject but still not working for us. We are making a simple signed makeRequest() with GET, These are the params we get on the server, //-------------------------------------------------------...

My code is working like so: var p = {}; p[gadgets.io.RequestParameters.METHOD] = gadgets.io.MethodType.POST; // post_data is a query_string, ie foo=bar&baz=url%20encoded p[gadgets.io.RequestParameters.POST_DATA] = post_data; p[gadgets.io.RequestParameters.AUTHORIZATION] = gadgets.io.AuthorizationType...

Summary: MySpace gives incorrect makeRequest signatures after requestNavigateTo to Canvas The basics: I have implemented signature verification correctly. If I visit my Canvas page manually (ie not using requestNaviagetTo, but rather by pasting the URL in my browser), MySpace signs the makeRequest parameters...

No doubt there's a lot of confusion in getting OAuth to work; it doesn't help that you're probably debugging against a boolean output. Thought I'd share my fustrations and "tips" on how I was able to get it working, in the hopes of saving someone from jumping off a bridget ...

The OAuth testing tool ( http://developer.myspace.com/Modules/APIs/Pages/OAuthTool.aspx ), when provided with the paramaters I recieve on my server, generates a different signature from what was provided in the request! consumerKey : "http%3a%2f%2fwww.myspace.com%2f330069419" consumerSecret...

Here is what I'm experiencing: - Signed POST requests to my server don't return my data. - Signed GET requests return data but pass query-string parameters TWICE to my server. Only my params get doubled not "oauth_" or "opensocial_" so I guess its a bug in how the proxy handles...

In summary, the problems with the makeRequest oAuth authentication appear to be: Empty oauth_token parameter. Empty oauth_signature parameter. Invalid oauth_timestap Are there additional issues that we need to be aware of?