[OSM-dev] OAuth difficulties from node.js client

Tom Hughes tom at compton.nu
Thu Jul 16 16:12:06 UTC 2020

On 16/07/2020 16:04, Nick Whitelegg wrote:

> Fiurthermore, if I use curl to send the same data to the endpoint, I 
> also get a 500:
> curl --data 
> "oauth_consumer_key=EcdM735JygrmO42fzw8SIfbFUMDy1ShVY5bBnefn&oauth_nonce=cNvPEgdgjvQWX5FgS56XkyLaMhQNggmh&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1594910535&oauth_version=1.0&oauth_callback=http%3A%2F%2Flocalhost%2Fapp%2F&oauth_signature=WuYA7G8s4qPCht%2BcF7t7FpTP0ck%3D" 
> https://www.openstreetmap.org/oauth/request_token
> I'm guessing something's wrong with the signing process. I used the 
> examples given in the oauth-1.0a documentation to generate the parameters.
> I'm surprised I'm getting a 500 rather than say a 400.

No that's normal - it's a bug in the OAuth library really but
getting a 500 if the client ID is invalid or the signature fails
is the "normal" behaviour as things stand.


Tom Hughes (tom at compton.nu)

More information about the dev mailing list