Hi
I'm just looking at the code and I'm wondering if the client you are
referring to in the original email calculates the signature correctly or
not. Is it RESTConsole ?
Basically, the signature string should have the parameters (including
the URI query parameters) separated from the base URI.
This page shows it quite well:
https://dev.twitter.com/docs/auth/creating-signature
I'm coming to the conclusion the problem is with the 3rd party client code
Thanks, Sergey
On 31/01/14 18:50, icoleman wrote:
Hi Sergey,
Thanks for taking the time to respond.
I was able to capture the raw headers as they passed through Fiddler (a
debugging proxy) and the successful authorization request looks like:
While the unsuccessful one generated by REST Console:
I did try to update the content type and accept headers for the failed
request to read...
...but that didn't seem to make any difference either.
--
View this message in context:
http://cxf.547215.n5.nabble.com/OAuth-1-0-And-Signature-With-Query-Params-tp5739357p5739361.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
