On 27/09/10 19:46, Matt Amos wrote:
On Mon, Sep 27, 2010 at 4:24 PM, Christoph Bünte
<[email protected]> wrote:
Ok, it seems to me, that I'am the only one having this problem. That makes me
think, that either I'm the only one who recently tried to connect an oauth
consumer with a provider. Or it is just a ruby issue, like some weeks ago, when
a new commit broke this functionality. Or, just to be complete, it is just me
having this problem at all, cause my code is somewhat faulty.
Could anyone try the example code with your app? Cause this issue keeps us from
starting our beta phase and publish wheelmap to a broader audience.
As always: Any help is highly appreciated.
it looks like oauth now needs the verification token from the callback
/ printed on the website when a token is authorised for OAuth 1.0a
support [1].
Yes, if you're using 1.0a then you'll need to provide the verifier -
that's one of the fundamental changes in 1.0a.
If you're using 1.0 then you don't have to, but we will be turning off
1.0 at some point so it's best to use 1.0a if you can.
Tom
--
Tom Hughes ([email protected])
http://compton.nu/
_______________________________________________
dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/dev
