Sorry for any inconvenience caused by the Signpost 1.2.1 release last week, which apparently regressed on callback URLs (see issue 34). That’s fixed in 1.2.1.1, along with another bug which prevented custom OAuth authorization headers to not be correctly interpreted before message signing.
Both should work fine now.
Have a nice weekend!
Advertisement
Matthias Käppler
Hi
I like the attitude and fastness in rectifying/fixing the bugs.
Comment by Charles — March 22, 2010 @ 9:47 am
Hi, is signpost capable of doing 2-legged oauth?
Of so can you guide me to a sampe code inside signpost? Regards, Carlos
Comment by Carlos — May 12, 2010 @ 4:09 pm
Hi,
yes you can simply leave the token + secret blank (i.e. not call consumer.setTokenWithSecret()). Requests will then be signed with the consumer secret only.
Comment by Matthias Käppler — May 12, 2010 @ 4:24 pm
I think custom OAuth authorization headers is still not honored due to behavior described in http://stackoverflow.com/questions/2864062/getrequestpropertyauthorization-always-returns-null.
The test case tested against a mock HttpRequest, which behaves differently from the actual one.
Comment by wyz — December 9, 2010 @ 5:17 pm