Don't add an oauth_token parameter to params. OAuthClient.invoke will
do that for you.
It's not necessary to set accessor.tokenSecret, if you set the
accessToken and tokenSecret. In this case, accessor.tokenSecret
should be the secret that the service provider sent with the access
token.
--
Yo
Hi,
I dunno how oauth in javascript works. I implemented oauth in
Java and I faced the same signature invalid issue. I broke my head for about
2 weeks before I found a solution. Anyways this was the problem. I was
running my app on a box which was sitting behind an apache webserver
mach
I needed another favour. I am trying to deploy the same gadget in
igoogle, but I keep getting invalid domain error. Could you help me
with this ?
On Feb 11, 9:24 pm, "mat...@gmail" wrote:
> You can replace hostname (or IP) included in signature base string before
> signing it.
>
> On 2010/02/12,
The issue is such that, we are hosting our own shindig container and
a web application in one box. The web application uses signed fetch to
render the gadgets and we are using the same codebase for the gadgets
deployed in public IP. When run within our web app using signed fetch,
the verification
See http://oauth.pbworks.com/ProblemReporting
Return a 400 with an error response with the acceptable_versions set to
1.0-1.0
I'm surprised at how much sloppy OAuth client code is out there...
On Fri, Feb 12, 2010 at 11:12 PM, Tosh Meston wrote:
> Hey everyone,
> I am seeing some requests to m
Hey everyone,
I am seeing some requests to my endpoints including oauth_version=1.0a
in the parameter list. As I understand the spec, if present, the
oauth_version parameter must be "1.0". What should we do if "1.0a" is
passed? Generate the signature with it and attempt a match? Return a
401 wi
